willsewell

7 ms·

31.
by willsewell 10y ago
From my understanding, the weak generational hypothesis holds for the majority of programs in general. In fact, it is particularly true of language that encourage immutable data ( because new data is created rather than existing data update
32.
by willsewell 10y ago
This is something we get asked a lot. The short version is that we had other requirements as well as a low latency. I described some of these here: https://www.reddit.com/r/programming/comments/5fyhjb/gol
33.
by willsewell 10y ago
There are already versions in: * C - https://gitlab.com/gasche/gc-latency-experiment/merge_reques... * C# - https://gitlab.com/gasche/gc-latency-experiment/merge_reques... * Nim - http:
34.
by willsewell 10y ago
That is the crux of the issue. I think the interesting thing about this benchmark is the degree to which different GCs assume the weak generational hypothesis to be true. For example, the Haskell/GHC GC seems to very much assume it, wi
35.
by willsewell 10y ago
I think we need to modify the benchmark to give enough time for the RTS to "warmup" before timing max pause times. This will provide a fairer comparison, since the end goal is to evaluate languages for web servers with large heaps
36.
by willsewell 10y ago
jcipar managed to get the max pause down to 22ms by tweaking parameters: https://www.reddit.com/r/programming/comments/5fyhjb/golangs... He also mentioned that the JVM GC does a lot of online tuning, so
37.
Golang's Realtime GC in Theory and Practice(blog.pusher.com)
8 points by willsewell 10y ago|0 comments