[Openstreetmap] Server Performance

Mikel Maron mikel_maron at yahoo.com
Sat Dec 31 11:14:28 GMT 2005

I think some of the response delay is due to the holidays, and Steve is feeling under the weather lately.

Tile Server/DB performance is a big big issue, and it's getting as much attention as possible 
(including myself, and I'm juggling a bunch of different drains on my attention).

For some background on the current architecture, problems, potential solutions...

The WMS configuration and vector drawing scripts are in...

Discussion is probably more appropriate on the dev list, but some brief thoughts. The needs are for short term optimization, long term rearchitecting, and more hardware. In the short term, we should look at replacing mapserver with a lightweight script .. it's presently only composting different WMS requests together. CPU intensive portions of the tile generation could be replaced with C code (it's possible to inline C in Ruby). In the long term, the architecture should support pregeneration and caching of tiles. Hence the need for more hardware.


ps Happy New Year!

----- Original Message ----
From: Etienne Cherdlu <openstreetmap-L at gj0.net>
To: openstreetmap at vr.ucl.ac.uk
Sent: Friday, December 30, 2005 10:55:12 PM
Subject: [Openstreetmap] Server Performance

The server performance is really really bad.

I've asked this question several times now and there's been no response.

What can we do about it?


Openstreetmap mailing list
Openstreetmap at vr.ucl.ac.uk

More information about the talk mailing list