Hi, I've merged back the memory_optmization branch. Please check if the merge is correct because I got some conflicts (and I am not a merge expert...).
Have fun! WanMil > In order to not get the merge lost ... I've been using the patched > splitter all along. Would be nice to see the trunk merged with the > memory optimization branch... > > On 30.11.2011 20:46, WanMil wrote: >> Hi, >> >> I've committed it. Do you think it's ready to merge back to trunk if >> noone complains within the next week? >> >> WanMil >> >> >>> Hello WanMil, >>> >>> during the last days I tried a lot of different techniques to further >>> improve memory usage, but nothing really improved the throughput >>> of splitter. The default settings are now so well tuned that the only >>> situation where --optimize-mem=true really helped was when spttiting rather >>> small files (pbf with 100MB or less). But these small files are never a >>> problem regarding memory, and I guess that most users that want to split >>> large files (europe or so) have machines with 8GB or more. >>> >>> So, the attached patch removes all code handling the --optimize-mem >>> parameter to remove useless complex code, keeping only those changes >>> that really improve something. >>> I've also added code to the unit tests and small correction to the now >>> unused SparseInt2ShortMap implementations. >>> >>> Ciao, >>> Gerd >>> >>> >>> >>> _______________________________________________ >>> mkgmap-dev mailing list >>> [email protected] >>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >> _______________________________________________ >> mkgmap-dev mailing list >> [email protected] >> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > _______________________________________________ > mkgmap-dev mailing list > [email protected] > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
