[mkgmap-dev] [PATCH v5]splitter memory usage
From Michael Prinzing mipri at gmx.net on Thu Nov 17 21:57:42 GMT 2011
On Wed, 16 Nov 2011 22:37:31 +0100, WanMil wrote: >I will merge the branch back to trunk after getting some feedback on the >list that the changes are worthy to merge. The patched splitter is the first version since r161 that is usable on my system (Win XP 32 bit, Java 1.7 , 1.7GB RAM). It is running very fast, with very low memory consumption compared with the unpatched r181 (which is using huge amounts of memory even for processing small areas). Moreover it is possible again to add contour data with node IDs higher than the max node ID from the OSM data which also did not work with r181 (not even with plenty of RAM). So for me there is no doubt that these changes are worthy to be merged to trunk. Thank you again Gerd for doing this. Michael BTW: Would it be possible to let the splitter decide if it uses 'optimize-mem' by default depending on the available heap space (no if there are more than 2GB available, yes with less than 2GB)?
- Previous message: [mkgmap-dev] [PATCH v5]splitter memory usage
- Next message: [mkgmap-dev] Markup for address search
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list