Opened 11 years ago

Closed 11 years ago

#3657 closed Enhancement (worksforme)

Make cache size configurable

Reported by: phoudiap Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 2.11
Severity: Normal Keywords:
Cc:

Description

hi coders of transmission, there should be an option to change the amount of cache stored in the RAM (like in the preferences)

That way, you can seed a file over night and not worry about your disk breaking over time.

There should be an option like: Maximum cache (where you type in a number of mega bytes) and a button that is like try and use maximum cache were possible. if it is unchecked, it will use minimum cache and run in low memory mode.

if you can do it, that would be great!

  • Philip Oudiap

United Kingdom

Change History (14)

comment:1 Changed 11 years ago by phoudiap

  • Milestone changed from 2.12 to 2.20

comment:2 Changed 11 years ago by charles

  • Milestone changed from 2.20 to None Set
  • Version changed from 2.11+ to 2.11

comment:3 Changed 11 years ago by charles

  • Summary changed from Cache to reduce hard-drive wear enhancement to Make cache size configurable

What OS are you using? You can already change the cache size by editing settings.json by hand.

comment:4 Changed 11 years ago by phoudiap

......

"blocklist-date": 1287678214, "blocklist-enabled": true, "blocklist-updates-enabled": true, "cache-size-mb": 2048,

......

it is still not using alot of RAM on my pc, and it is still reading my harddrive

Last edited 11 years ago by phoudiap (previous) (diff)

comment:5 Changed 11 years ago by phoudiap

maybe for future use there should be a cache option in the preferences section of the program. Good idea?

comment:6 Changed 11 years ago by Rolcol

The implemented cache is for written data. Perhaps you really mean to use it for reads also?

If you have a torrent actively downloading, Transmission will use the 2GiB cache you've set. I'm willing to bet that you want it for reads, too.

Last edited 11 years ago by Rolcol (previous) (diff)

comment:7 Changed 11 years ago by Longinus00

The cache will flush itself of completed pieces whenever resume data gets written. The reason for this is that transmission doesn't really know the difference between data in the cache and on the disk so if the system crashes the resume data will be all wrong.

comment:8 Changed 11 years ago by phoudiap

yeah i want it for reading, so when i seed it wont always use my hard drive.. is this possible for a future update?

Last edited 11 years ago by phoudiap (previous) (diff)

comment:9 Changed 11 years ago by phoudiap

  • Summary changed from Make cache size configurable to Cache for reading / Make cache size configurable

comment:10 follow-up: Changed 11 years ago by charles

  • Summary changed from Cache for reading / Make cache size configurable to Make cache size configurable
  1. Two separate ideas belong in two separate tickets
  1. The cache is already a read/write cache

comment:11 in reply to: ↑ 10 ; follow-up: Changed 11 years ago by phoudiap

Replying to charles:

  1. The cache is already a read/write cache

but it accesses my harddrive when im seeding, am I doing something wrong? RolCol? says its a writing cache only.

my cache is set at 2048 and im trying to seed a 350mb file, in which it still accesses the hard drive.

Last edited 11 years ago by phoudiap (previous) (diff)

comment:12 Changed 11 years ago by Rolcol

I'm not all-knowing (that'd be charles), and I'm known to get things wrong.

You're still going to get some disk access. How else is it going to know what to share? Brute forcing the correct data would the age of the universe. In that case, disk access is good.

comment:13 in reply to: ↑ 11 Changed 11 years ago by charles

Replying to phoudiap:

Replying to charles:

  1. The cache is already a read/write cache

but it accesses my harddrive when im seeding, am I doing something wrong?

No. Just because you have a cache doesn't mean it's going to read in the entire torrent when you start seeding. It's going to read the pieces in as they're requested from peers, and remember them.

Rolcol says its a writing cache only.

Rolcol is wrong.

comment:14 Changed 11 years ago by jordan

  • Resolution set to worksforme
  • Status changed from new to closed

Closing this ticket since the cache size already is configurable by editing settings.json.

Note: See TracTickets for help on using tickets.