Message boards :
Number crunching :
Nbody issues with CPU only processing
Message board moderation
Author | Message |
---|---|
Send message Joined: 18 Aug 09 Posts: 122 Credit: 21,008,416 RAC: 355 |
Guys, What is the average CPU time used by the current Nbody taks when using just a CPU? Also what is the average credit granted? My system (using version 6 of BOINC) with a quadcore cpu, chews these tasks up in just a matter of a few minutes and then gives me only 1 credit. This in turn drags my average down. I am wondering how my machine can chew through 43,000+ 'bodies' in such a short amount of time. Or is Nbody more of a GPU task? What do you GPU users see for credit and time spent crunching? |
Send message Joined: 18 Aug 09 Posts: 122 Credit: 21,008,416 RAC: 355 |
Guys, That's it... I am not accepting any more Nbody tasks. They just drag my credit into the ground. Sorry guys, but since you can not answer why a CPU machine is getting dinged so badly for that kind of task, other than the task is completing "normally" to paraphrase, I am just going to take whatever PS work you send out. It seems Nbody is more of a GPU task from the looks of things. |
Send message Joined: 6 May 09 Posts: 217 Credit: 6,856,375 RAC: 0 |
That's not how Nbody WUs should behave - is anyone else having this problem? I recommend making sure that you have the latest version of the Nbody code. There may also be another system-specific issue at hand. The Nbody code is currently CPU-only. We will be working on extending it to GPUs this summer. Hopefully we can get this working for you. -Matthew |
Send message Joined: 18 Aug 09 Posts: 122 Credit: 21,008,416 RAC: 355 |
That's not how Nbody WUs should behave - is anyone else having this problem? Thanks for looking into this. Check my results and system info and if you have any questions send me message. |
©2024 Astroinformatics Group