[Geocoding] Nominatim performance

[Glenn Plas]

On 08-03-14 11:20, Cambridge Cycling Campaign - Simon Nuttall wrote:
> A whole world nominatim installation started on 2 Feb finished on 7
> Mar, and is now running at:
>
> http://nominatim.cyclestreets.net/
>
> It has entered the catch up phase - which began with data from 21 Jan.
>
> It seems to be taking a day to catch up with a day's updates - so it
> is not making much progress and is heavily i/o bound, even on a 32GB
> VM with 2 allocated processors.
>
> Do all these timings seem normal?
>
> What could I do to improve performance?
>
> Simon
>
> _______________________________________________
> Geocoding mailing list
> Geocoding at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/geocoding
Most Virtual Machines lack IO performance.  Even if underlying storage 
consists of SSD's, you're only getting a slice of it.   I would suggest 
to assign a few more VCPU's , 2 seems a bit low.   But this sounds like 
a true I/O related issue.

A 'real' machine with 32GB on performant SSD's is probably the minimum 
for a planet import.  (I believe 64GB is recomended for this sort of 
install).  I would definitely blame IO limits here.

Glenn

-- 
"Everything is going to be 200 OK."