[OSM-dev] Run away Ruby and Postgres optimization

Brendan Morley morb.gis at beagle.com.au
Mon Sep 13 22:49:59 BST 2010

What parts of the API are you exercising?

When setting up servers for CommonMap, I found that a 50,000 element 
upload takes 40 to 80 minutes to complete, depending on the type of 
server I used.

Ruby on Rails is very inefficient for that kind of thing.


On 14/09/2010 6:15 AM, Eric Wolf wrote:
> We finally have our system running and are doing some field tests with 
> multiple editors. The system keeps getting bogged down. Looking at the 
> process list, I'm seeing 7-8 ruby tasks, each eating 50%-100% of a CPU 
> core (thank god for multiple CPUs & cores). They are persisting for 
> 20+ minutes. Any idea what may be up? Should ruby tasks be hanging 
> around that long?
> I'm running a pretty much default Postgres install. Any hints on 
> optimizing Postgres for OSM?
> -Eric
> -=--=---=----=----=---=--=-=--=---=----=---=--=-=-
> Eric B. Wolf                           720-334-7734
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20100914/46c1de85/attachment.html>

More information about the dev mailing list