Can't get BOINC to use all CPU cores...

[Grall]

Blagh!

It uses just one single core for some reason, despite I've set 100% of CPU use all the time, in every preferences/config setting I can find.

Anyone have any idea why it's doing this?

Also, is SETI@Home dead as a project? Not getting any work, so I attached to Milkyway instead. Gave up on Folding, its clients are so bizarrely shit I just can't bother with that anymore. Still looking for a truly worthwile alternative, but until I find one I must get the client to utilize my system properly...

 

[Grall]

Oh... Now it's doing it. No idea why it changed its mind all of a sudden, lol. All 8 threads active, alive and well. However it doesn't utilize graphics cards in parallel with CPU cores, that's a bit shite. So now it's doing 8 CPU tasks and 0 GPU tasks. There's like 15 GPU tasks queued up and just sitting there, waiting to be executed, and considering how much horse power there's in a GPU that's a huge waste of resources.

 

[Davros]

about seti, maybe they found life..

 

[Grall]

Haha! Yeah, well, their project seems to be floundering tbh. Reading up on their site you see their servers have poor reliability, news updates are far between, there's - as I percieve it - a general air of pessimism about the whole thing. And my boinc client is in on the third day more or less without any work to do, so I guess they're about to close up shop or something, I dunno.

Milkyway started using my GPU btw, I forgot there's an option that pauses work while the system is in use. It did a couple packets, then got stuck for some reason aborting prematurely for whatever reason. Both GPUs would abort simultaneously, then start over on another packet. I turned the whole thing off, then decided to update drivers, as I think I was running a version from like novermber or december of last year or something... Maybe that'll improve matters, I dunno. Maybe not, I don't think ATI did much with their CAL driver at the end, and now I believe they've aborted any further development entirely in favor of OpenCL. Maybe they still bugfix, I dunno.

 

[Grall]

I've studied the boinc client a bit more closely now. Each time the GPUs pause for user activity, it tosses away all work done so far, but in fact doesn't start on a new packet. It just starts over and over on the same packet. So if you keep interrupting it, it won't ever actually finish that packet... Fortunately they're pretty small, so as long as my PC gets a couple minutes just sitting there unmolested, it will chew through the packet just fine.

Weird thing - in a good way: Boinc detects both GPUs even with crossfire, and without hooking up a monitor to the second board, and without extending the desktop... Folding@home on the other hand can't handle any of those things. It can't run multi-GPU with crossfire on, you must connect monitors to all boards (under vista/win7), and you need to extend the desktop - which causes confusion when the mouse pointer slips off the screen and onto another invisible monitor (I used to cheat while folding and just hooked up VGA to the same monitor...)

Also, Boinc supports x64 too, which folding does not. However I dunno if this actually help with anything in reality.