*.tah.openstreetmap.org - Why HTTP persistent connections disallowed?

View: New views
2 Messages — Rating Filter:   Alert me  

*.tah.openstreetmap.org - Why HTTP persistent connections disallowed?

by GeoJ :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

while playing around with a HTTP proxy I noticed that the tiles@home
servers *.tah.openstreetmap.org explicitly disallow to use persistent
connections by sending the header "Connection: close" in the response.

For a regular http server with small web pages (small number of files
per webpage) this would not be a problem but those servers also act as
server for the generated tiles. A common map view in the browser
consists of ~20-40 tiles and for each tile the browser has to establish
an separate TCP connection - this is very inefficient and resource
consuming.

Wouldn't it be better to allow HTTP persistent connections or is there
some problem with it I do not recognize?

GeoJ


_______________________________________________
Tilesathome mailing list
Tilesathome@...
http://lists.openstreetmap.org/listinfo/tilesathome

Re: *.tah.openstreetmap.org - Why HTTP persistent connections disallowed?

by Sebastian Spaeth :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

GeoJ wrote:

> Hi,
>
> while playing around with a HTTP proxy I noticed that the tiles@home
> servers *.tah.openstreetmap.org explicitly disallow to use persistent
> connections by sending the header "Connection: close" in the response.
>
> For a regular http server with small web pages (small number of files
> per webpage) this would not be a problem but those servers also act as
> server for the generated tiles. A common map view in the browser
> consists of ~20-40 tiles and for each tile the browser has to establish
> an separate TCP connection - this is very inefficient and resource
> consuming.
IIRC we did try this earlier, but then a client would be able to occupy
a download slot for a lot longer, making others time out who also want
to get tiles. This is more resource consuming yes, (but the server copes
fine), but it allows more clients to get tiles within a short time span.

I could try to go back to pipelining, but afaik it was causing more
problems than it was solving.

spaetz



_______________________________________________
Tilesathome mailing list
Tilesathome@...
http://lists.openstreetmap.org/listinfo/tilesathome

signature.asc (268 bytes) Download Attachment