06-05-2010, 08:02 AM
I normally run the Distributed.net client on my desktop. It's setup so it will only utilize CPU cycles unused by other applications (i.e. a low priority task), but keeps the CPU 100% utilized continuously. I normally don't notice a performance impact related to running it, but I do see a significant impact with Dolphin. I'm guessing the constant 100% CPU utilization is causing Windows to not assign the Dolphin threads to separate CPU cores appropriately.
In any case, thought I'd throw this post out to note to folks that distributed computing applications can have a significant impact on Dolphin performance, even if they are set as low priority tasks. Shutting them down while running Dolphin can help avoid some performance issues.
In any case, thought I'd throw this post out to note to folks that distributed computing applications can have a significant impact on Dolphin performance, even if they are set as low priority tasks. Shutting them down while running Dolphin can help avoid some performance issues.