Cacher is the code snippet organizer for pro developers

17:47 < warner> hm, there's a bunch of advice we can give. As for actual written-down stuff.. hm. 
17:47 < warner> There's a wiki page called "Atlas perf" where I measured performance of a bunch of files of various sizes
17:47 < warner> but that was mostly looking at differences between download algorithms
17:48 < warner> both uploads and downloads have a certain amount of overhead that's independent of the filesize
17:48 < warner> it's sort of an A + B*log(size) + C*size equation
17:48 < warner> where A might be between 100ms and 500ms plus maybe 4 or 5 roundtrips
17:48 < warner> and B doesn't much matter because it's swamped by C
17:49 < warner> and C is like 5-10MBps or the speed of your wire, whichever is lower
17:49 < warner> but in general I'd say that anything 1MB or larger should be fine
17:50 < warner> I'd avoid doing lots of <1MB files, as the round-trip-time and startup overhead starts to matter
17:51 < warner> and I'd avoid gigabyte-sized files just because they'll take forever to upload, and if you lose one of the 
                storage-server connections during that time, the share is abandoned
17:51 < warner> (someday we'll have a way to resume those, but not yet)
17:51 < warner> hope that helps!