Ian Dees schrieb:
On Wed, Sep 10, 2008 at 3:16 PM, Ed Loach <[EMAIL PROTECTED]> wrote:I think this is an improvement; it means we seem to have clients ready to start servicing the level 1 and 2 requests almost as soon as they come in (when all is running smoothly that is), and the level 4 requests are getting dealt with without the upload queue filling and causing everything to choke up.But this means my CPUs are sitting idle with no work to do, and I'm paying for their power and heat to do nothing. I'd rather see them doing preemptive renders of highly-edited areas or rendering those prio4 requests than sitting idle.
The queue length does not determine the processing speed at the server. Doing pre-emptive rendering of highly edited areas will only lead to unneccessary load at clients and server, and possibly outdated tiles.
How many requests per second is the TAH server able to handle? It doesn't seem like shuffling this sort of data around would be too much work, but I didn't pay attention to those huge discussions about tileset-per-file earlier. Did we cover this issue then?
The server stores the tilesets in single files, but there is no single number we can put as "tilesets per hour" or per second, as this varies greatly with what the clients upload.
The main concern with the tah server currently is stability, and secondly the OSM API is not keeping up with us anymore (we have taken steps to remedy this, thanks to Florian Lohoff we do have good fallbacks for the API now).
-- Dirk-Lüder "Deelkar" Kreie Bremen - 53.0952°N 8.8652°E
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
