Re: [mkgmap-dev] Performance hints for Java JRE 9 + 10
Hi, i have comparable performance to former Java 8 and considerable lower memory consumption, when i use the OpenJDK 10 with the Eclipse OpenJ9 VM from AdoptOpenJDK! It is not officially released jet, but i use it with great success. If you want to try, you'll have to use the nightly builds from AdoptOpenJDK: https://adoptopenjdk.net/nightly.html?variant=openjdk10-openj9 Best regards and happy trying, Uli ;) -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Performance hints for Java JRE 9 + 10
Hi Felix, I am not sure but I think a JRE 8 will not execute a jar file compiled with JDK 9 or higher. So, I was only talking about using a newer JRE. I don't know when we will start to compile with 9 or higher. If I got that right JDK 9 is no longer available, so we probably have to switch to 10 or higher. Gerd Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von Felix Hartmann <extremecar...@gmail.com> Gesendet: Mittwoch, 16. Mai 2018 16:05:50 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Performance hints for Java JRE 9 + 10 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_muenc...@hotmail.com<mailto:gpetermann_muenc...@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<mailto: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 ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] Performance hints for Java JRE 9 + 10
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 Petermannwrote: > 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 ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
[mkgmap-dev] Performance hints for Java JRE 9 + 10
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