Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command execution turns very slow with current amount of upk/log files #5

Open
darkhellsatan666 opened this issue Jun 26, 2019 · 0 comments

Comments

@darkhellsatan666
Copy link

darkhellsatan666 commented Jun 26, 2019

First of all, thanks for your grat tool, i'ts been really helpful for many ppl.

About the issue, currently is a nightmare update the tool, it have problems handling too many files (~>40k files) the problem occurs with upk_scanner and upk_parser, not sure if is directly a problem with the amount of files or when surpasses certain amount of ram (over 2.8 gb aprox), to be clear my system ram is 16gb.
A workaround, at least for me is divide the scanning and parsing process in two sessions (using 2 groups of upk/log files), backup the resulting 1st session files (log/json) and combining manually with the 2nd session ones, however i'm sure that this generate it's own issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant