Skip to content

per cpu results ( per unit metrics ) - responses per second per cpu #9971

@ar-daniel

Description

@ar-daniel

This website benchmark is very helpful, appreciate your efforts.

In the website page showing the framework results table - It would be nice to have an adjacent column prior to responses/ sec result column, which can additionally show the result in responses /sec /cpu
this value is effectively the result of the total responses divided by the total cpu cores used in the test ( including the virtual cores )

also can mention some where at the start of the results table - the cpu frequency at the time of testing ( eg 2.2 GHz )
as base processor frequency of Intel Xeon Gold 6330 CPU range from 2.00 GHz which can be turbo clocked upto 3.10 Ghz
if cpu frequency is changed ( or got changed accidentally ) for each test ( or framework ), then accordingly cpu frequency can be mentioned against each test and framework.


In the round 23, the server environment mentioned in the website is

3 homogeneous machines equipped with Intel Xeon Gold 6330 CPU @ 2.00GHz (56 cores) ( incl hyper threading )

as for now if I had to find it myself,
lets say a framework xyz has result of 1,200,000 responses/ sec
to get per cpu result, should I divide 1,200,000 / 56 to get 21,428 responses /sec /cpu core ? or
divide by 3 machines total cpu count = 1,200,000 / (56 x 3 ) to get 7142 responses /sec /cpu core ?


In addition the description of each test can be mentioned below test title ( fortunes, single query, JSON serialisation etc ) and above the results table.
this can help understand how each test is done


plus the results shown are only from physical hardware machine i guess
https://www.techempower.com/benchmarks/#section=data-r23

results that are run with cloud environment machines are not seen in website
may it got missed somehow in being showing up in the webpage

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