Skip to content

benchmark logging #1026

Open
Open
@sdarwin

Description

@sdarwin

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:

Screenshot from 2024-07-17 17-44-40

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.

date +'%Y/%m/%d %H:%M:%S:%3N' >> /tmp/json-benchmarks.log
echo "Starting to process canada.json with clang" >> /tmp/json-benchmarks.log
lscpu -e >> /tmp/json-benchmarks.log
top -b -n 1 | head -n 20 >> /tmp/json-benchmarks.log

(run benchmark)

After processing a json file.

date +'%Y/%m/%d %H:%M:%S' >> /tmp/json-benchmarks.log
echo "Finished processing canada.json with clang" >>  /tmp/json-benchmarks.log
lscpu -e >> /tmp/json-benchmarks.log
top -b -n 1 | head -n 20 >> /tmp/json-benchmarks.log

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions