On Sat, Aug 02, 2003 at 10:07:00PM -0600, Wesley J Landaker wrote: > All theory and token tests aside, here is some *real* data. I have a > cooksync-like script (but written in ruby and multithreaded) that I've > used for at least the last six months, and I have *always* had it spit > out the stats. In fact, because I'm morbidly curious, I *always* look > at them. Typically, I get AT LEAST a 20-30% speed, often it's more > than 50%. > For reference, here is the stats part of the output for the last > synching session. For the record, this is typical, not a special case > or a fluke or something I dragged out of all the bad ones just because > it looks good. They are *all* this good.
The problem with this as an example is it includes unversioned uncompressed files like: compss provides depslist.ordered Additionally you're getting the synthesis and hdlist files. When you take and add those up you come up with about 34MB of data. When you look at your matching data it comes out to 31MB or so. Makes me wonder if the hdlist and synthesis files aren't rsyncing well. I should run some experiments to see how well that works... Unfortunately the explanation of the format in the packdrack man page is rather lacking. I've saved a copy of my base dir and I'll see what I can come up with for testing tomorrow. But I'm highly suspicious that all of that speed up is from moving the files around. It just doesn't fit the data and the protocol... -- Ben Reser <[EMAIL PROTECTED]> http://ben.reser.org "What upsets me is not that you lied to me, but that from now on I can no longer believe you." -- Nietzsche
