[OSM-dev] API down?

[Raphael Jacquot]

Nick Hill wrote:
> I would like to see stats of how much processing demand each slippy map 
> user puts on tile with the current set-up, and suggestions how we can 
> improve the efficiency of tile serving.
> 
> Currently, the burden each slippy user puts on tile is unclear. tile 
> does lots of things. Once we move the tile rendering off to another 
> physical machine, i'll have a better idea of what sort of demands each 
> slippy map user puts on tile.
> 
I had another idea.
how about adding a tiles table in db that would have a few flags, and a 
rendering process. the thing would work so :

while 1:
	begin transaction
	find first dirty non-busy tile (using a dirty flag)
	set tile busy
	commit transaction
	grab tile data
	draw tile
	save file(s?)
	begin transaction
	set tile not dirty
	set tile not busy
	commit transaction

the tile dirty flag would be set when something gets modified on the tile
the rendering process in question could be run parallelly on multiple 
machines.
then you only need to serve the already rendered pictures from a 
machine, a la google