3 ms·
actually comparing jitted vm's without a warmup is extremly dump. Second: using the default thread dispatcher for this kind of scenario is pretty dumb on scala
by merb 11y ago
actually comparing jitted vm's without a warmup is extremly dump.
Second: using the default thread dispatcher for this kind of scenario is pretty dumb on scala (also I think erlang could be made faster, too. but since I'm not an erlang guy...) Fixed Thread Pool (GOMAXPROCS vs ForkJoin)
- atemerev 11y agoAll timers are started after the warmup.
- mafribe 11y agoHow do you know when warmup is finished? Warmup's a tricky issue, see this brand new paper: http://arxiv.org/abs/1602.00602 http://arxiv.org/abs/1602.00602
- wizzard0 11y agoThere's an update for Akka version, which measures 12/8/4.4 seconds on subsequent attempts, so yes, warmup is important... but somehow that seems kinda unfair for other languages too.
- dtech 11y agoNo? In the scala code the timer is started and Actors are created. No warmup anywhere. https://github.com/atemerev/skynet/blob/master/scala/src/main/scala/Skynet.scala#L33 https://github.com/atemerev/skynet/blob/master/scala/src/mai...
- BrandonBradley 11y agoI agree that using the default thread dispatcher is not how this should be used. The application's actors should create and use its own ExecutionContext.
- BrandonBradley 11y ago/cc @atemerev