Skip to content

The actual use of file_pool_size #6439

Answered by arvidn
DJPlaya asked this question in Q&A

You must be logged in to vote

In the documentation, it is just described as useful for virus scanners, so my main question is if there is any good use in having a high number set in the settings for performance.

The reason there is a pool is to avoid high costs to open and close calls. Both of those can become very expensive with virus scanners, but also on MacOS with HFS+, close() can be extremely slow. In more recent versions of libtorrent, it's not just open and close, but also mmap and munmap calls that are saved by caching them in the pool. I'm less familiar with how kernels normally handle frequent mapping and unmapping, but there's a risk each call have to alter the page table and could be somewhat expensive.

Replies: 1 comment

You must be logged in to vote
0 replies
Answer selected by DJPlaya
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants