Dude, it's a double Etc. day! What the heck??
I've sent Cyril out on assignment, so news may be... nonexistent for the rest of the day. So here you have me.
I mentioned a WorldBench problem in my earlier Etc. post. This doesn't look like an issue that will be easily resolved, and it's one in a string of issues with big, scripted tests like that. I may end up dropping WorldBench or just reducing our use of it to a few of the most interesting tests. That might open up room for a few new tests in our CPU benchmark suite, which currently looks largely like what we used in our Lynnfield review, with the exceptions that I've switched to four newer games and updated some applications.
You guys often have suggestions for CPU tests we might try. Unfortunately, I often forget them between the time you make them and the time we go to re-work our test suite, which only happens a few times a year. Also, many of those suggestions present real problems for various reasons. I'm willing to do some of the work in sorting out a new test, but it has to be practical and workable. Here are a few criteria that help determine whether a test will work for us:
That's about it, I think, but I reserve the right to add more conditions at will as your suggestions clarify our needs. Within that framework, I'm happy to take suggestions, although if they're just, "You should test Photoshop," well, thanks, Skippy, but there's more to it than that.
|Asus and Sapphire offer digital pickaxes to crypto-miners||13|
|Rumor: Six-core Coffee Lake CPU pops up in Geekbench||12|
|Nokia 6 comes to the US with a taste of vanilla Android||10|
|SNES Classic will fix your nostalgia blues this September||25|
|Corsair reveals its prize haul for the TR BBQ XIV||7|
|Portions of the Windows Shared Source Kit leak out||13|
|Hyper-Threading erratum rears its head in Skylake and Kaby Lake||51|
|VR180 video bridges the gap between YouTube and VR||4|
|Steam 2017 Summer Sale, part deux||19|