3 ms·
> Would be interesting to have a raw comparison to the JVM e.g. to the new GC1 And with Shenandoah [1] too! Also, everyone talks about heap sizes; which is ki
by BenoitP 10y ago
> Would be interesting to have a raw comparison to the JVM e.g. to the new GC1
And with Shenandoah [1] too!
Also, everyone talks about heap sizes; which is kind of the size of the problem if you let it accumulate. I would be much more interested in having these latencies measured in the context of sustained allocation throughput, with varying object lifetime lengths. How much the system can take while staying afloat? Here is the most performant gc: never allow to allocate anything.
Go programming constrains heavily towards message passing. I guess this is some kind of tradeoff. I really hope it still makes a lot of new apps possible (40k users concurrently interacting multiplayer games, anyone?).
[1] http://openjdk.java.net/jeps/189 http://openjdk.java.net/jeps/189
- pjmlp 10y agoGame studios have been using GC enabled languages for their servers for quite a while now. For example Wooga has quite a few games using Erlang, Hallo used C#/Project Orleans, just to cite two examples.
- BenoitP 10y agoOh, definitely. And Whatsapp is able to maintain 2.8M connections, > 200k msgs/sec on one machine with Erlang [1]. I meant not in an embarrassingly parallel worload. The 40k would be with interacting with each other in realtime, and not by groups maxed at 10-20. Each of the 40k being impacted by the other 40k's actions; with an all-reduce step between them at each tick. Each of them getting a different overview of the other 40k. Imagine a FPS where users receive updates on others' position 60 times per second if they are close, 1 time per second if they are far away, and none if the player is not looking at them. This could enable vastly larger games. The question at hand would be: Go and Erlang's GC enable great latencies; but can their programming model still enable this worload easily? What kind of degree of shared mutable state do we need? [1] http://highscalability.com/blog/2014/2/26/the-whatsapp-architecture-facebook-bought-for-19-billion.html http://highscalability.com/blog/2014/2/26/the-whatsapp-archi...