[postgis-users] Geocoding very slow (minutes)

[Stephen Woodbridge]

If you have not already done some tuning of postgrresql with respect to 
memory usage, I highly recommend doing this as postgresql by default 
does not use much memory. google: postgresql tuning
Specifically look at increasing shared_buffers but other params might be 
helpful ti increase also.

-Steve

On 6/21/2015 8:32 AM, Wayne Seguin wrote:
> Brand new installation of PostgreSQL 9.4.4 with latest PostGIS as an
> Extension and 2014 tiger data. 100% loaded and indexed.
>
> Geocoding any address is taking 1-2 minutes per. Something is wrong, but
> no way to tell what. Checked and all data and indexes are present.
> System is a 4-core 16Gb ram, SSD-based machine.
>
> SELECT * FROM geocode(normalize_address('4150 International Plaza Fort
> Worth TX 76109')) As g;
>
> Might have narrowed it down to the big select at the end of the
> geocode() function, but since I do have all indexes, I'm at a loss to
> figure out what's wrong.
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
>