We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, during the download of a torrent users will see spikes in memory usage equal to the block size of each torrent every once in a while. This is due to the fact that we just allocate some buffer on the fly (https://github.com/GGist/bip-rs/blob/master/bip_disk/src/disk/tasks/helpers/piece_checker.rs#L53) which has a size equal to the piece length.
With a 2MB piece length, this will spike process usage exactly 2MB (for that torrent), which is less than ideal.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently, during the download of a torrent users will see spikes in memory usage equal to the block size of each torrent every once in a while. This is due to the fact that we just allocate some buffer on the fly (https://github.com/GGist/bip-rs/blob/master/bip_disk/src/disk/tasks/helpers/piece_checker.rs#L53) which has a size equal to the piece length.
With a 2MB piece length, this will spike process usage exactly 2MB (for that torrent), which is less than ideal.
The text was updated successfully, but these errors were encountered: