Blizzard Goes and Pulls the Rug out from my Testing

So I’m doing a lot of subjective testing with WoW and a few different setups, trying to get a feel for how it performs before moving onto another game or two. All just play through stuff, far too much of the game to actually be fun, really.

And what does Blizzard do halfway through my framerate runs to figure out what influences the gameplay? Change the general settings.

So. Now I’ve gotta go pull a few rigs out and go through all the World of Warcraft game testing again.

Although one thing seems to have had a fairly big affect. Turning off the tickless kernel option and switching to the CFQ scheduler from deadline seems to have cleaned up some I/O inconsistency issues. Now it gets a bit catchy in odd spots (like when you’re taking off on a flight path) but the overall performance is fairly consistent and doesn’t hang up on any particular points when fighting or actually playing.

So far it’s been a pretty good experience with the current release of WINE.

World of Warcraft as a Benchmark of GPU Performance (on Linux)

So WINE and WoW do, in fact, make a good benchmark of system performance for Linux. Unfortunately I’m now butting up against the fact that it absolutely and sometimes erratically flatlines the system.

It doesn’t kill the box, but I’m seeing 100+% CPU usage runs on the dual core. This creates a slight problem.

So… I need to actually find some machinery that can run WoW (or whatever I end up benchmarking with for the article) at something under full throttle.

That and I need to cobble together a Windows release for some cross platform testing. I’m not positive it’ll perform any better under the native OS, but I am pretty sure the driver support on the video side will be more refined.

Ah well. Back to hacking.