On 14-Oct-12, at 5:31 AM, Iván Sánchez Ortega wrote:
On Sunday, 14 de October de 2012 10:05:31 Paul Norman escribió:
I'm giving a talk tomorrow on ogr2osm [...] For a 600 MB .mdb (400
MB .shp)
[...] it uses about 6-7 gigs of ram for that. I may be able to get
that down
substantially, I haven't really attacked the RAM usage yet.
Well, that's the problem I want to tackle down (and it's possible
to tackle it
down). You just need some mechanism to free nodes from memory when
you're sure
all the overlapping geometries have been proccessed.
Please do let me know how the ogr2osm talk goes.
My target is to be able to create 2G .osm files without hitting swap
on my home server (16G ram). Past that you run into problems with
handling the output file even if ogr2osm can handle . I suspect
there's a lot of low-hanging fruit for the memory usage. Right now I
don't believe *any* memory is freed up so it's keeping around
everything even when it's done with it. By default ogr2osm creates an
in-memory copy of the data source to allow it to be changed
(necessary for some translations) and using the command-line option
to disable that would reduce the memory usage.
_______________________________________________
dev mailing list
dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev
