Printable View
I removed and reinstalled Poem in a Win7, x64, AMD A8-3870k, XFX 6870 system with app_config set to 1 CPU for every 0.5 GPU. 1 WU ran for 18,000 seconds, completed and validated. 31,200 credits a day compared to over 250,000 a day on the retired project. (The computer was running other CPU projects plus being used for Internet surfing and youtube watching).
FYI, the 6870 is a single precision card and the 7790 is double precision.
Running 2 at a time on the TITAN, this time without any CPU tasks running:Quote:
Originally Posted by zombie67
Task run time = 5,500 seconds. That works out to ~202k/day. So 3 is the best.
In comparison, running with 2 GPU tasks 1 full thread each AND filling up the remaining threads with CPU tasks was 133k/day. That is a SIGNIFICANT hit to production. Now I need to run some more tests to see if I can run some number of CPU tasks before the slow down kicks in.
I think I may know what's going on. Are your tasks being suspended at all? Like maybe they are suspending when you use the keyboard? Or running benchmarks, or rebooting? These tasks seem to very sensitive to that kind of stuff. Mine sometimes error out when just changing the number of GPUs in the app_config.xml. Maybe by not changing anything, or doing anything that causes the tasks to suspend at all, you can get them to complete?Quote:
Originally Posted by FourOh
Just a guess, but i'm gonna say the slowdown begins at the point where the number of cores used by the GPUs, plus the number of cores used by CPU WUs exceeds the number of cores the CPU has, either pushing the GPU tasks to a HT thread, or trying to cram it together on the same core/thread as a CPU WU.Quote:
Originally Posted by zombie67
My A8-3870k/7790 system is a dedicated cruncher. Crunched straight through without interruption and errored. Two more guesses left. :)Quote:
Originally Posted by zombie67
BUT WAIT!!!!! I have Collatz GPU tasks on that machine, too, and Boinc may have switched between POEM and Collatz. I'm running another POEM on the same machine and suspended Collatz. Please stay tuned.
(Leave applications in memory while suspended is enabled).
I also note that my A8-3870k/6870 had Collatz and POEM GPU tasks, and it was being used for surfing, youtubing, Excelling, NotePadding, and Doc-ing, all while POEM was running and the WU completed and validated. It was also running Ibercivis at the same time.
My A8-3870k/7790 WU erred again. No interruption of crunch. It was only 65% through the crunch at 7160 seconds. Using BM 7.2.33. Will try 7.2.42
My A8-3870k/7790 WU erred a third time. No interruption of crunch. Using BM 7.2.42. No success on this card. It has OpenCL but no CAL.
tried this one ?
http://developer.amd.com/tools-and-s...ssing-app-sdk/
They used those things years ago and I read something recently that it could be useful for the new ones too.
I tried running the poem app on my gtx 570 and everyone errored out. Went back to gpu grid.
Thanks, conf. Love your new avatar. Maybe Four-Oh will give this a try. I just try things and if they don't work, I move on. :) Lots of projects do work well without fussing.Quote:
Originally Posted by conf
Is not so bad, just install it.
The Sculpture is from my master not by myself, just cleaned it several times. He is dying having Parkinson this days
and got nearly blind. Would honor him this way though it makes me sad.
So, I have two machines with dual 7970s. One crunches the new POEM stuff great, the other nothing but errors. The successful one is running 14.3 beta drivers. The other was 13.12, I think. Anyway, I did a scrubbed uninstall and then installed 14.3, and it is now crunching POEM successfully. No idea if that was just a coincidence or because of the driver upgrade. But for those with failing AMD tasks, try it.
False alarm. The first few tasks validated. All the rest errored out.Quote:
Originally Posted by zombie67
Yep. This always happens when project launch a new app on Fridays.
Quote:
Message 9540 - Posted: 24 Mar 2014, 18:33:03 UTC
Hi everybody,
I'm afraid the release turned out to be a mess. There are much more problems than we have seen on the test server.
The worst thing was my own fault: I thought turning off the GPU sorter would suffice to get work units out of the queue, but in fact all failed units were sent out again. Sorry for that, which I should have known.
It should now be fixed.
I'll grant credits for jobs which failed after taking CPU time as soon as possible.
We do now know possible causes for the errors, and are fixing them. There will be a second test phase, but I can't give you a schedule yet.
Thomas
So MSP is one of Maxwell's relatives.......?Quote:
Originally Posted by Duke of Buckingham
If anyone cares, poem is testing gpu wus again. They have separate test server you need to connect to, I think. Check their site for details.
You don't get any credits but the rest of us will supply you with atta boys :DQuote:
Originally Posted by EmSti
Notes on the new GPU app so far:
Project updater needed to get wus flowing
Only running on the R9 295x2, increased from 1 wu per r9 290x gpu to 2 wus per gpu and it took no more time. Double the credit same amount of time. Keeping about 4 cpu threads free for the 4 wus. Completing 4 wus every 2.25 hours (11,555 credits an hour, on collatz the card produces ~130,400/hr).
Usage is still less than 100% on the GPUs, I haven't tried 3 or more wus.
Power usage and heat are a lot less than collatz (not hard to do).
Thanks for the heads-up on this. I need to get back to Poem, and this'll be useful...Quote:
Originally Posted by EmSti
Quote:
Originally Posted by EmSti
We have another thread on the new app with run times, etc here:Quote:
Originally Posted by Maxwell
http://www.setiusa.us/showthread.php...Project-Status
Thanks for the tip
Continuing my notes on the other thread.