Hi Gerd, What about if you compile mkgmap with java 9 or higher - and run it on Java 8 - this also applies or not? Or asked differently - is this dependant on the compilation system or on the executing system? Felix On 16 May 2018 at 15:53, Gerd Petermann <GPetermann_muenchen@hotmail.com> wrote:
Hi all,
it seems that the new Garbage Collector (G1GC) that was introduced with Java JRE 9 causes longer run times for splitter and mkgmap. I've played with some options and found that the use of -XX:+AggressiveHeap seems to be a good idea when you use these newer JREs.
Without this option the java programs tend to allocate more memory and thus the OS might start to swap.
Gerd
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Felix Hartman - Openmtbmap.org & VeloMap.org Schusterbergweg 32/8 6020 Innsbruck Austria - Österreich