To the degree feasible given the breadth of submissions we've received, we have worked to ensure that frameworks that use process-level concurrency are configur

To the degree feasible given the breadth of submissions we've received, we have worked to ensure that frameworks that use process-level concurrency are configured to in fact use multiple processes. See question #5 from our questions section [1]. That said, across the board, inclusive of both process-concurrent and thread-concurrent frameworks, we never rule out the possibility of a configuration glitch. We've asked that any subject-matter experts for any framework perceived as underperforming review the code and configuration. To date, we've received a great deal of pull requests to deal with many such matters. On the other hand, very few such tweaks have had a significant impact on performance data. We do intend to capture CPU, network, and IO utilization in the future. For the time being, we invite fans/SMEs to review the code, run the tests on their own multi-core machine and/or EC2 instances and determine if there is room for improvement. [1] http://www.techempower.com/benchmarks/#section=motivation http://www.techempower.com/benchmarks/#section=motivation