If you’re gonna try doin’ benchmarks for sim-baking, keep one thing in mind:
While your typical rendering-benchmark is usually about rendering a still (not an animation), baking a physics-sim means Blender will write a file to disc after simulating each frame.
The point is: In your usual rendering-benchmark no data is written to disc, and even if, then just once in the end. Thus the time it takes to write the framebuffer to disc is neglectible.
Now if you’re baking a sim, it’ll write the data to disc afer each frame, so the time it takes your hdd to write this data adds to the raw computing-time your cpu has to spend.
In short, if you want to do sim-baking benchmarks, you should probably consider checking what hdd you’re using, maybe gather some technical data about it (how fast does it write according to the manufacturer?).
I’m by no means trying to imply you could kind of calculate the time it takes to write the data to disk and then substract this from your benchmark’s results in order to know the raw computing-time. This would quite sure not work out, be confusing and rather useless anyway.
But I think it might make a notable difference if s.o. were e.g. using the exact same system for your benchmark, only once writing the files to an hdd at 5400 upm and once one at 7200 upm.
In any case I heared it makes a big difference weather you bake to an hdd or an ssd (the latter is obviously much faster).
So to sum it all up: Other than knowing what CPU you used 4 baking, it’d be probably good to know about the hdd either, to get usefull, comparable results from this.