Comment 3 for bug 165061

Revision history for this message
Vincent Ladeuil (vila) wrote :

Some infos :

Regarding:

We do 4 readv's of the pack during fetch:
http readv of 2a0e5ecbd9eea5a28df78a003ced30a4.pack offsets => 14689 collapsed 294
http readv of 2a0e5ecbd9eea5a28df78a003ced30a4.pack offsets => 14689 collapsed 295
http readv of 2a0e5ecbd9eea5a28df78a003ced30a4.pack offsets => 33490 collapsed 671
Retry "2a0e5ecbd9eea5a28df78a003ced30a4.pack" with single range request
http readv of 2a0e5ecbd9eea5a28df78a003ced30a4.pack offsets => 5650 collapsed 114

http already collapsed some offsets, the raw numbers before that are:
'http://bazaar.launchpad.net/%7Elifeless/bzr/repository/.bzr/repository/packs/' replaced by <base> below
Transport.readv(<base>,'2a0e5ecbd9eea5a28df78a003ced30a4.pack',4029)
Transport.readv(<base>,'2a0e5ecbd9eea5a28df78a003ced30a4.pack',15361)
Transport.readv(<base>,'2a0e5ecbd9eea5a28df78a003ced30a4.pack',31598)
Transport.readv(<base>,'2a0e5ecbd9eea5a28df78a003ced30a4.pack',33485)

So your first two readv look strange :
http readv of 2a0e5ecbd9eea5a28df78a003ced30a4.pack offsets => 14689 collapsed 294
http readv of 2a0e5ecbd9eea5a28df78a003ced30a4.pack offsets => 14689 collapsed 295

It's as if they are both related to "my" second readv but 294 != 295 and I can't find an explanation for that difference.