[Tilesathome] Render Queue getting bigger

Gregory Williams gregory.williams at purplegeodesoftware.co.uk
Tue Sep 18 19:03:32 BST 2007


>From what I see on my t at h client I'd say the obstacle is that there are
no more than 50 jobs running at any one time, not the two OSM processes.
My t at h client spends most of its time idle, waiting for a request from
the t at h server, rather than most of its time waiting for data from the
API.

Gregory

-----Original Message-----
From: tilesathome-bounces at openstreetmap.org
[mailto:tilesathome-bounces at openstreetmap.org] On Behalf Of Robert Hart
Sent: 18 September 2007 18:54
To: Dermot McNally
Cc: tilesathome at openstreetmap.org
Subject: Re: [Tilesathome] Render Queue getting bigger

> Can somebody who knows more outline what the true obstacle is here,
> and whether I or anybody else can help?

As I understand it, the limit is not the number of clients. The main
OSM API has been restricted to two server processes for all T at H
clients, and the T at H server has been set to hand out no more than 50
jobs at once. Depending on the ratio of download time to render time
one or other of these factors is the limit (I suspect the two OSM
server processes)



-- 
Robert Hart

_______________________________________________
Tilesathome mailing list
Tilesathome at openstreetmap.org
http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome





More information about the Tilesathome mailing list