You've exposed the fact that old cpus are old!

It's a classic case of a "collector" suddenly finding out that his priceless treasure-trove of priceless relics is just a room full of junk.
You've really got two choices. Keep benchmarking using code that your team built 5 years ago on a 5 year old PC, with a 5 year old compiler, library files that are at least 5 years old and the settings used 5 years ago. And never, ever, change it because it's more holy than the Holy Grail.
Or update your benchmark and let the tears fall where they may.
I say that you come out with a new version every month and just flush the results that are over a month old.
That way you can optimize its utility and usefulness without having to worry about how different the scores are from earlier versions on earlier hardware.
And that way it is more likely to remain RELEVANT.
Unless you want to peg it to a K5 at 10 or something, as someone suggested earlier, laugably.
Like it's only good if a K5 system scores a 10 on it
Maybe run it by NIST to get the proper scores.
Or should we go back to the days when benchmarks would score lower on AMD chips than Intel simply because the compilers didn't recognize AMD chips as fully Intel compatible and so would revert to using standard x86 calls instead of SSE calls? Or should you try every compiler, compiler setting and compiler version out there until you get a Ryzen 5 to beat a Xeon gold?
You can't go around worrying about what will make these fanbois happy, that will just hobble your benchmark with a label of being biased towards Intel or AMD, for or against modern CPUS and so on. Pick a goal and code to it. then defend the goal and the coding.
cheers
Leave a comment: