[Geocoding] Nominatim disk usage
Frederik Ramm
frederik at remote.org
Fri May 20 08:14:52 BST 2011
Hi,
I was wondering who else is running a planet-wide, minutely-updated
Nominatim instance, and share some experience.
Speficially, I'd be interested to hear about disk usage because I have a
hunch that my installation consumes more than it should.
I have everything in a special "nominatim" tablespace (and nothing but
Nominatim is there), and the partition now uses 727 GB (with G=1024^3).
Postgres seems to confirm that, again roughly:
nominatim=# select pg_size_pretty(pg_database_size('nominatim'));
pg_size_pretty
----------------
728 GB
(1 row)
My tables are sized like this:
# select relname,
pg_size_pretty(pg_total_relation_size(relname::varchar)) from pg_class
where relkind='r' and relnamespace=2200 order by
pg_total_relation_size(relname::varchar) desc limit 10;
relname | pg_size_pretty
-------------------+----------------
place_addressline | 276 GB
placex | 113 GB
search_name | 75 GB
planet_osm_nodes | 69 GB
planet_osm_ways | 67 GB
place | 37 GB
search_name_2 | 28 GB
search_name_3 | 14 GB
search_name_1 | 4971 MB
location_road_2 | 3664 MB
(10 rows)
I would like to find out if that is roughly what others are seeing too.
I'm running PostgreSQL 9/PostGIS 1.5 on a system that otherwise is
Debian Lenny.
Bye
Frederik
More information about the Geocoding
mailing list