[tahoe-dev] Tahoe benchmarking data

[David-Sarah Hopwood]

Brian Warner wrote:
> On 7/25/10 8:10 PM, Kyle Markley wrote:
>> I wonder whether temporary file creation for the small file transfers
>> might be part of the problem.  I know that temporary files are created on
>> occasion; could someone explain precisely when?
> 
> There aren't very many. The most relevant one here is that "large" HTTP
> request bodies (the threshold is 100kB) are held on disk (instead of in
> RAM) between the HTTP PUT/POST request and the actual
> encrypt+encode+push upload. [...] The other two places are:
> 
>  * when you do a download with a Range: header that doesn't cover the
>    whole file, the 1.7.1 code creates a temporary file to hold the
>    incoming data (and then does seek()+read() to return just the desired
>    segment).
>  * if you're using a Helper, then the helper holds encrypted upload data
>    on disk until the ciphertext transfer is complete and it can start
>    the real encode+push.

Just for completeness, the FTP and SFTP frontends also create temporary
files when you use those frontends for an upload.

-- 
David-Sarah Hopwood  ⚥  http://davidsarah.livejournal.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 292 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20100726/72fe5421/attachment.pgp>