Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add memory/GC statistics to Socket/Tls benchmarks #6

Open
Drawaes opened this issue Aug 31, 2017 · 0 comments
Open

Add memory/GC statistics to Socket/Tls benchmarks #6

Drawaes opened this issue Aug 31, 2017 · 0 comments

Comments

@Drawaes
Copy link

Drawaes commented Aug 31, 2017

While throughput/overhead for a "raw" test is the most important metric and this is currently covered.

GC/Allocations are also important. Especially when sockets/TLS are used in the scope of a larger application and in resource constrained environments (Docker for instance).

What we see is on servers that are under stress with full workloads, where the user code is already churning the memory GC can take a significant percentage of the processor time.

To this end I would recommend that during a benchmark there is an option to spit out GC information. This could be done at the start and end to get a "snapshot" or at each of the intervals.

If you are interested in this I could have a crack at somestage to prototype something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant