Two temporary download folders so I can process smallish downloads in memory

[lpmccracken]

I would like to be able to keep downloads under 2 GB (or whatever amount fits with your available memory) in memory (i.e. /dev/shm), the rars, any pars, all the raw downloaded parts, then unrar, also in memory, then finally move the unrared files to the final location.

This would allow me to have smallish downloads processed in memory only, which should be faster, but more importantly, saves disk writes.

Downloads over 2 GB would be processed in a separate location, namely somewhere on a hard drive.

There should probably be big warning messages about how a 2 GB download will take at least 4 GB to fully process & proceed with caution & be sure you have enough available memory available for this.  Also, maybe some warning about how power failures & shutdowns & reboots will empty this memory-based temporary download folder with malice.

Thanks.

[shypike]

Right now, having a large enough article cache will reduce disk access.
Further than that we cannot go, since par2 and unrar both want disk files.
Your only option would be a RAM-drive.

[lpmccracken]

No problem on the RAM disk, but I'd like to have two areas for different sized downloads.  Temporary download location #1 is the RAM disk & has a required field where I set the size of downloads that get processed on temporary download location #1.  I define Temporary download location #2 as a location on a hard disk for downloads that are larger than the size I have set above.

My article cache is can be 100MB or 200 MB or whatever size the largest single rar part or par2 part is that I typically download, then those parts get moved over to the RAM disk where the par2 & unraring take place.  I haven't done any tests, but a par2 repair is disk write intensive, is it not?.  Maybe nothing is saved from unraring to the RAM disk then moving the file to the final output folder versus just unraring to the final output folder.

This RAM disk/second download location should also speed things up.  The parity check has to do disk reads, which have to take extra time.  If it's in memory, then that will be lightning fast.

I hope I've been clear in requesting two fields for defining two separate Temporary download locations plus a field for a size (MB, GB, both, other) whereby downloads less than or equal to the size are processed in Temporary download location #1 & downloads larger are processed in Temporary download location #2.

Currently, if I define my one Temporary download location as a RAM disk, I can't download anything larger than 7 GB.

Thanks again.