[Geocoding] Disk space consumes 2GB per month
Sarah Hoffmann
lonvia at denofr.de
Wed Oct 16 21:07:29 UTC 2013
Hi,
On Wed, Oct 16, 2013 at 09:38:55PM +0100, Simon Nuttall wrote:
> I've noticed that on our Europe wide nominatim installation the
> available disk space is declining by about 2GB per month.
>
> Is this a known issue?
That sounds like normal growth. The osm.org instance has grown
by around 200GB in the last year. Part of it comes from the
regular growth of OSM data, part from index bloat.
> What can be deleted?
You can try to play with the autovacuum parameters of postgres
to be more aggressive with vacuuming which might help a bit
with the table/index bloat. The most problematic indexes are
idx_search_name_name_vector and idx_search_name_nameaddress_vector.
poldi has actually a cron job running that vacuums the search_name
table once per night because of that. It helps a bit but the indexes
have to be recreated nonetheless from time to time when their size gets
out of hand.
Sarah
More information about the Geocoding
mailing list