On 2/9/11 2:38 PM, David-Sarah Hopwood wrote: > On 2011-02-09 19:29, Brian Warner wrote: >> On 2/9/11 12:20 AM, sreenivasulu velpula wrote:
>>> + Encode And Push: 37 seconds (7.6kBps) >>> # Cumulative Encoding: 7.4ms (31.6kBps) >>> # Cumulative Pushing: 24ms (10.0kBps) > It seems strange that Cumulative Pushing is such a small proportion of > Encode and Push. From the descriptions above, I would have expected it > to be the majority. What is the other contribution to Encode and Push > that isn't included in Cumulative Encoding and Cumulative Pushing? # Send Hashes And Close: 36 seconds "Cumulative Pushing" only includes the encoded blocks, but "Encode And Push" includes "Send Hashes And Close". I think something went wrong during the last few roundtrips and everything stalled. The new immutable downloader has much finer-grained timing information, so you'd be able to tell exactly which request was stalled. (and the Protovis-based gantt-chart makes that data easy to understand). My plan is to eventually port that timing framework to the uploader too. cheers, -Brian _______________________________________________ tahoe-dev mailing list [email protected] http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
