[Tilesathome] Rate Limiting & be gentle with you requests

[Frederik Ramm]

Hi,

> I think we need to concentrate on directly making sure that T at H  
> clients
> don't overload the API.

Easy solution 1:

Have the t at h server request the data from the API for each tile that  
is requested; do this with a queue runner process; hand out the  
render request together with data to the next client asking for work.  
Does not increase total traffic, and makes sure that there's never  
more than one request at the same time. Works only if t at h and API are  
in same LAN, otherwise doubles traffic.

Easy solution 2:

Set up replication and have t at h clients load their data from the slave.

> Another thing that would help is if the server didn't send complete
> ways, only complete segments when serving to a T at H client. JOSM likes
> complete ways, but T at H doesn't need them, and they impose a huge
> processing overhead on the server.

Especially if we're cutting a tile into 10 narrow stripes as we do  
now - this leads to a lot of data being downloaded multiple times!

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00.09' E008°23.33'