Big speed difference for G1 vs. parallel GC

2016-10-31 Thread Peter
Hi, I've stumbled today* over a big speed difference for code execution with G1 GC vs. parallel GC also in the latest JDK8 (1.8.0_111-b14). Maybe you have interests to investigate this. You should be able to reproduce this via: # setup git clone https://github.com/graphhopper/graphhopper wget htt

Re: Big speed difference for G1 vs. parallel GC

2016-10-31 Thread Bernd Eckenfels
Hello, Since this is measuring a short workload after vom startup it might not be the best benchmark, but then again throughput GC is expected to be faster than G1. In the particular case however I guess you could tune G1 a bit to that workload. Did you check the verbose GC logs, and how many CPU

Re: Big speed difference for G1 vs. parallel GC

2016-10-31 Thread Peter
Hi Bernd, why do you think it is measuring a short workload? 'short' in which terms? The overall test suite takes roughly 3 minutes but can be increased easily via increasing the number of road routing queries. BTW: with routing.mean we measure the latency of every road routing query, at least I t

Re: Big speed difference for G1 vs. parallel GC

2016-10-31 Thread Vitaly Davidovich
G1 has more expensive GC write barriers - if you have a reference heavy heap with lots of mutation, it can add up. 20% more overhead for each barrier is a number I've heard before. On Monday, October 31, 2016, Peter wrote: > Hi Bernd, > > why do you think it is measuring a short workload? 'shor