[bhauer]

Yes! In fact, I just responded to a similar question over at the Rust Subreddit thread about the same topic.

We do in fact capture dstat data while executing the tests but as of today do not render these in any way. You can find raw CSV output from dstat at our logs server. For example at [1] are stats for Grizzly while measuring the "json" test type.

I will create an issue at the project's GitHub repo to begin a conversation about which stats to render. I'd like to select a meaningful bite-size set of stats that we can render into a table view. Basically another tab in the results view similar to the latency tab.

[1] http://tfb-logs.techempower.com/round-16/final/grizzly/json/...

[drunner]

If I could make a recommendation that would humor me personally, you could publicize the stats required to run the instance on an B1S or Fv2 Azure instance.

I think it would be really interesting to see which frameworks are so costly upfront that they would impede a developer from prototyping with them on the cheap.

[bhauer]

I like that idea. I'll see what we can do!

[tomaha]

That's great. Thanks.