[OSM-dev] Exhaustion of 32bit signed integer range expected this year
Frederik Ramm
frederik at remote.org
Sat Apr 14 11:22:32 BST 2012
Hi,
On 04/13/2012 04:42 PM, Simon Poole wrote:
> It seems as if it would really make sense to make the 64bit ID version
> of osm2pgsql the default now and communicate that it might be a good
> idea to switch on the upcoming reload.
>
> Do we have any idea what the actual impact on DB size etc is?
I have just run a series of osm2pgsql benchmarks (on a system equipped
with SSDs and 32 GB RAM, PostgreSQL 9.1). A standard osm2pgsql import
with --slim looked like this:
32bit IDs 64bit IDs
time for planet load 38956s 45955s
bytes required on disk 276594360 284217608
So you're roughly looking at at a 15% penalty in speed and only about 2%
in disk space. (I haven't benchmarked updates or rendering yet.)
Bye
Frederik
--
Frederik Ramm ## eMail frederik at remote.org ## N49°00'09" E008°23'33"
More information about the dev
mailing list