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

Crush poor system #86

Open
ashkov opened this issue Jul 21, 2017 · 1 comment
Open

Crush poor system #86

ashkov opened this issue Jul 21, 2017 · 1 comment

Comments

@ashkov
Copy link

ashkov commented Jul 21, 2017

When I run telegram-history-dump on aws micro with 1Gb Mem, the system stop answer after dumping approximately 30000 rows.
I think, it is necessary to add configuration option to split initial download by chunks and repeat it several times until end. And make memory free each time

@tvdstaaij
Copy link
Owner

This is indeed a problem with the current release and large dialogs (also see #57). I already implemented a fix that should work but hasn't been tested thoroughly yet, see #74. You can try that version by switching to its feature branch (git checkout dump-old-to-new). Note that this branch contains semver-major changes and requires a fresh backup (delete the output directory first if it exists). If you want to try this it would be appreciated if you report your findings in issue #74.

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

2 participants