[OSM-dev] running a local server

[Jon Burgess]

On Fri, 2007-11-02 at 16:14 +0100, Frederik Ramm wrote:
> Hi,
> 
> >  - t at h uses way more resources to render, and is much slower. You
> > couldn't realistically use osmarender to produce real-time rendering
> > of tiles, but mapnik is fast enough to do this, and requires much less
> > memory to run.
> 
> To give some numbers: I used to run a nightly re-render of the whole  
> Karlsruhe area (5 by 5 level-12 tiles, for a total of 34125 tiles),  
> rendering one normal and one mapnik layer, on a reasonably up-to-date  
> dual-core Athlon with 2 GB RAM (but I did not run anything in  
> parallel). The job usually started around 4:00 MET at night and  
> finished at 8:30 MET; that includes the time used for downloading the  
> data from the API.

The 'weekly dump' is not an inherent limitation of Mapnik renderer. It
is possible to download data via the API for say a z12 tile, import it
with osm2pgsql and then render all the tiles for that z12 square (and
higher) to produce 'real-time' rendering using Mapnik.

The main OSM Mapnik layer is not run like this because it is more
convenient to import the whole planet and render tiles on an adhoc
basis. The underlying tools will let you render any set of tiles from an
OSM file whenever you want.

	Jon