[Geocoding] Data importing problems.
Sarah Hoffmann
lonvia at denofr.de
Mon Jul 10 20:52:56 UTC 2017
Hi,
On Mon, Jul 10, 2017 at 09:27:29AM +0300, Andrius wrote:
> Hello,
>
> I installed nominatim on a new server with "Centos 7 OS", 'Intel(R) Core(TM)
> i7-4770 CPU @ 3.40GHz' 16GB of RAM and now I'm trying to import data of
> Europe (europe-latest.osm.pbf from http://download.geofabrik.de/. I use
> flatnode file for importing and import already consumed 250GB of disk and
> import is still running after 6 days.
The size is to be expected but the import time seems overly long. If you
don't use SSDs then this is a likely cause as a good IO performance is
crucial for the import. Otherwise I'd look again into tuning postgres
settings.
> And import porcesses:
>
> Difference between installation which you are providing is that we are
> running Nominatim on 'nginx' instead of 'apache', but I don't think that it
> can harm something.
>
> Now nominatim is already available on our server, but reverse geocoding
> responses in about 5 seconds. My question is:
It is not a good idea to run queries while the import is still running.
There are a lot of indexes still missing which are important for search.
So you end up with a lot of sequential table scan which make not only
your queries slow but also have a negative impact on the import in
progress. Once the import is finished you will see much faster responses.
Kind regards
Sarah
More information about the Geocoding
mailing list