dumb http servers make packs perform very badly

[Vincent Ladeuil]

bialix reported that using tracd on windows (itself using the python HTTP server) responds to range requests by sending back the *whole* file.

The urllib implementation crashes bzr while pycurl is very slow.

[John A Meinel (jameinel)]

It is a valid response based on the HTTP spec. We just need to figure out a way to prevent our performance from becoming horrible.

We also have poor scaling when the number of packs become large, but maybe a way to be less aggressive on repacking for specific repositories?

[Vincent Ladeuil (vila)]

Ranges are a HTTP 1.1 addition, so yes a 1.0 server MAY reply that way.

[Vincent Ladeuil (vila)]

The fix is vailable in bzr.dev and will find its way in bzr 1.1

[tebeka (miki-tebeka)]

Using bzr.dev as of today (Dec 23, 07), I still have the same error as in https://bugs.launchpad.net/bugs/177613

[Vincent Ladeuil (vila)]

Can you attach the relevant traceback and tell us more about the http server you're running against (brand, version) ?

[tebeka (miki-tebeka)]

Hello Vila,

> Can you attach the relevant traceback and tell us more about the http
Same traceback as in initial post.
(I've switched to a smart server now and deleted the HTTP "dump"
configuration ...)

> server you're running against (brand, version) ?
lighttpd 1.4.18

All the best,
--
Miki Tebeka <email address hidden>
http://pythonwise.blogspot.com/
The only difference between children and adults is the price of the toys

[Vincent Ladeuil (vila)]

I installed lighttpd 1.4.18 and found a bug (#179368) regarding multiple range requests.

Subscribe to it if you want to be kept informed on progress.