[OSM-dev] Tiles at home - current disk use

Hakan Tandogan hakan at gurkensalat.com
Sat May 19 17:07:51 BST 2007

> 1: we could block access to the old disk. This means that PHP is never called 
> for tile-viewing and everything goes through mod-rewrite
> 2: we could specifically request the whole world, so that the new disk fills. 
> (I don't know if anyone is trying to do this already). 
> 3: we could remove old tiles from the exported list of tile metadata. This 
> would cause various peoples' scripts to request any tiles where OSM has data 
> but tiles at home doesn't. 
> Currently I'm inclined to test option 1 first, to see what effect it has on 
> performance.  
> We should really do 2 or 3, so that we get stuff rendered asap, especially if 
> it means that more requests go through mod-rewrite rather than PHP.

In the spirit of keep-it-simple, I'd say that we remove all access to 
the old disc (1) and re-request the whole world (2).

I seem to remember a mail to -talk from a while ago that we would need 
only a few days to re-render the whole world.

Maybe we could limit the maplint layer even more (say, only levels 
12,13,14) if it makes the complete re-rendering faster. After that, we 
can re-enable the higher zoom levels because the areas people are 
interested in (and are working on) will be automatically re-rendered.


The Key To Immortality Is First Living A Life Worth Remembering.

More information about the dev mailing list