Jim,
I think you’re referring to this reference.conf
https://github.com/akka/akka/blob/master/akka-actor/src/main/resources/reference.conf
which has this section of the scheduler settings:
# Used to set the behavior of the scheduler.
# Changing the default values may change the system
I think the OS you're using matters a lot for this sort of test. Hopefully
it's not windows...
What was the maximum concurrency level that you've tested?
Did you make sure (in the performance test code) that this concurrency
level is actually met in all cases?
Did you try tweaking with the
Hi Jim,
I will certainly track down that example Spray app and take a look; however, my
understanding of the Scheduler’s tick-duration configuration field is that it
only affects scheduled messages. Since I’m not using the scheduler’s interface
at all, I figured that setting was irrelevant.
Hmm. Then I must have been playing with the setting around the same time. It's
definitely related to overall thread scheduling. Poke around the reference.conf
files in the core akka jars. There should be a description of the overall
methodology in there as well. Timer granularity and number of
