-
Notifications
You must be signed in to change notification settings - Fork 92
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
benchmark logging #1026
Comments
If it's simpler to implement, not all of the above commands are required. Imagine another shell script running in the background on the server, that once-per-second repeatedly measures the cpu frequency,
Then Considering further, perhaps the output is similar to what it's already outputting:
except,
|
Ok, I can do that. |
Testing a new benchmark machine. "The (Hetzner) EX44 Dedicated server’s hidden gem is the Intel® Core™ i5-13500 processor."
Ubuntu 24.04. CPU year 2023.
After numerous optimizations, this is an example benchmark:
It appears there are two instances of unknown disruptions even though most services have been locked down. Nothing else would be using that processor since it's isolated by cgroups. The newest intel processors may only be taking the scaling frequencies as a suggestion, and occasionally override the choice.
The benchmark command is
./bench -i:b *.json
.The following idea may or may not help, it would be an experiment. Could the benchmark executable
bench
itself be enhanced, by calling external shell commands, before and after each file (apache_builds, canada, citm_catalog, etc.) ?Log output to /tmp/json-benchmarks.log
Before processing a json file.
(run benchmark)
After processing a json file.
The text was updated successfully, but these errors were encountered: