Hello Olaf, thanks for the confirmation.
So if this high memory usage is not considered as a bug (but as a feature) I think it would be a good idea to avoid the resize actions when the highest node id is known before. If I understood it right, the first pass could save this information for each processed area. Also, this info could maybe be used to determine whether the available max. heap is large enough to use this feature, else the normal hashmap can be used. I'll try this and post a patch if it helps. Ciao, Gerd -- View this message in context: http://gis.638310.n2.nabble.com/splitter-memory-usage-tp6935688p6938817.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
