[Tilesathome] API Bottleneck

[80n]

Sebastian
The current bottleneck for t at h appears to be the throttled API.  Hopefully
this will ease a bit after the NL upload is complete, although there will
still be plenty of load from the TIGER upload.

I'm wondering if we should consider a mechanism whereby priority 2 requests
are serviced by the Zappy API.  Currently a lot of the priority 2 requests
are taking over a week to get processed so the Zappy API would be just as
good even though it's data is up to a week old.

I would need to make a small change to extend the Zappy API to recognize the
/api/0.4/map?bbox= style of request, but that is pretty trivial.  There
would also need to be a change to  tilesGen.pl to tell it where to get the
data from.

Perhaps then all pending priority 2 tiles that are unprocessed each
Wednesday evening could automatically be flagged as being renderable by the
Zappy API.

80n
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tilesathome/attachments/20070920/d7c55bad/attachment.html>