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

Disk state optimization: separate queue and history #207

hugbug opened this issue Apr 23, 2016 · 0 comments


None yet
1 participant
Copy link

commented Apr 23, 2016

Currently the download queue and history are stored in the same file on disk (queue).

The size of download queue can be seen as relatively constant. The history however grows over time. The queue must be written into disk pretty often - after every downloaded included file (typically a rar-file). The history on the other side is changed much less often - after the whole nzb-file is downloaded. This discrepancy leads to much more often writing of history data into disk than necessary.

That can result in a performance decrease if history is very large but the disk is very slow.

Solution: To avoid potential performance degradation the queue and history should be stored in separate files.

@hugbug hugbug added the feature label Apr 23, 2016

@hugbug hugbug added this to the v17.0 milestone Apr 23, 2016

hugbug added a commit that referenced this issue Apr 23, 2016

@hugbug hugbug closed this Apr 23, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.