[Tilesathome] Render Queue getting bigger

[Dermot McNally]

On 18/09/2007, Sebastian at sspaeth.de <Sebastian at sspaeth.de> wrote:
> it seeems, it got much slower since a)the api server restricted the
> number of request slots from unlimited to 3 and b) sine our amount of
> data in the db has basically doubled within a week and will continue to
> grow as quickly as the server can take it (TIGERand AND)

This makes sense up as far as it goes, and I've certainly seen cases
where my own copy of t at h (running locally, not under instruction) will
time out an API connection. I'm normally on the other side of the slow
API (waiting for JOSM to download what I want), so I'm certainly not
going to suggest adding to a busy queue.

However:

1. Regardless of whether it makes sense for my installation to join
the rendering pool, to allow me to see my own maps, I've rendered
quite a few tiles manually. It would seem to make sense for me to
upload these - if so, can anyone here issue me with a username (I
requested one from Ben, but he may have considered it non-urgent in
the circumstances).

2. Might there be value in a modification to the client that would
allow the API request to target a larger bounding box encompassing a
number of adjacent tiles? This would need work on the server, clearly,
to instruct the clients as to when to do this, but it might be a way
of maximising the impact of a successful request. (downside: bigger
bounding box = more server load).

Dermot