cache-size-mb只涉及到内存写入缓存，不能设置读取缓存？所有上传经过硬盘导致io高负载

[1265578519]

cache-size-mb只涉及到内存写入缓存，不能设置读取缓存？所有上传经过硬盘导致io高负载
我查看了配置文件，都没有详细说明读取缓存
https://github.com/transmission/transmission/wiki/Editing-Configuration-Files

监控也很明显的，全走磁盘，不经过内存

[1265578519]

版本 2.84

[mc256]

Translate:
cache-size-mb can merely set the writing buffer but make no controls on reading buffer, which makes seeding a problem.

The user @1265578519 wants to configure the reading buffer so that the program can load the entire file to memory for seeding purpose.

[mc256]

版本 2.84

发英文比较好

[xavery]

cache-size-mb is only used for (re-)calculating the hashes. It is not used for I/O during peer messages at all. If you grep through the code, the only references to tr_cache{Read,Prefetch}Block that you're going to find come from functions which are used for calculating hashes for the torrent's pieces. The cache is filled while the pieces are received from peers (presumably for recalculating the hash when the torrent is completed, though I haven't checked that in depth), but isn't used at all when sending data to them.
The only form of caching used while sending data to peers is POSIX's fadvise call. Transmission does not appear to use any form of internal caching in this case.
It seems like the meaning of this configuration key is very widely misunderstood. I wish there was a wiki page or something that users can be pointed to in order to familiarise themselves with what cache-size-mb actually does, or, more importantly, what it doesn't do.

[1265578519]

@xavery 我认为，他是确实有写入缓存的，因为你尝试修改值，然后进行下载操作，你会发现，在设置的值内，不会写入硬盘，都存在内存中。
如果达到内存值满了，才会进行一次硬盘的写入操作。

[xavery]

@1265578519 You're welcome to open the code and prove me wrong. I'm just sharing my own experiences, since I've looked into this before.

[mc256]

I would suggest closing this issue. This is not a programming issue.
The wiki page might need to be updated.

[Shados]

cache-size-mb is only used for (re-)calculating the hashes. It is not used for I/O during peer messages at all. If you grep through the code, the only references to tr_cache{Read,Prefetch}Block that you're going to find come from functions which are used for calculating hashes for the torrent's pieces. The cache is filled while the pieces are received from peers (presumably for recalculating the hash when the torrent is completed, though I haven't checked that in depth), but isn't used at all when sending data to them. The only form of caching used while sending data to peers is POSIX's fadvise call. Transmission does not appear to use any form of internal caching in this case. It seems like the meaning of this configuration key is very widely misunderstood. I wish there was a wiki page or something that users can be pointed to in order to familiarise themselves with what cache-size-mb actually does, or, more importantly, what it doesn't do.

For anyone looking into cache-size-mb behaviour: the quoted comment was incorrect at the time of writing, and still is. I'm not sure how the OP missed it, but the cache was and is used for both prefetching and reading blocks in response to peer messages, since right back from its initial implementation in 2010 (look at the diff for libtransmission/peer-msgs.c).