I wouldn't exactly call EQ a cpu-intensive program. Look at resource monitor or perfmon when you zone.
While zoning back and forth into gfay from BB, on my crappiest box with slowest CPU (affinity set to a single core on a dual core processor), the biggest "spike" i see only hits 50% for a literally a split second during the 15-18 seconds it takes to zone. The CPU is basically flatline the rest of the time. I guess my closer analysis just now has ruled out s3d / eqg file compression as the bottleneck being that the CPU isn't doing anything for the majority of the time.
So what the heck is it doing for the other 16-17 seconds? Some forced wait in the client?
PS. Revodrive may technically be driven by a "software" raid controller chip, but it's gonna run circles around your velo setup with CPU time to spare.
[You must be logged in to view images. Log in or Register.]