Posts by Microcruncher*

1) Message boards : Number crunching : Best Linux Distro To Crunch With (Message 1123909)
Posted 2 Jul 2011 by Profile Microcruncher*
Post:
Then again, leaving Boinc to run at the default "nice 10" already grabs almost all of the CPU for an idle system. You can't use more CPU instruction cycles than exists, regardless of process priority!

Certain combinations of Linux, CUDA drivers and science apps (Just 2 examples: The PrimeGrid AP26 CUDA application and old versions of the Collatz CUDA app) ran significantly slower if the priority of the CUDA app was greater than 0. As soon as all CPU cores were under load (the CPU processes were running at the lowest priority) the GPU starving began and the performance dropped noticeably because the GPU was not fed fast enough. In some cases the runtimes more than doubled if the CUDA process wasn't reniced to 0.
2) Message boards : Number crunching : Beta testers BoincTasks for Linux and Mac (Message 1118989)
Posted 19 Jun 2011 by Profile Microcruncher*
Post:
Wine version: 1.3.22 - compiled from source
Linux distro: Debian 6.0 squeeze
Architecture: amd64
BOINC version: 6.10.58 / Debian 6.0 distribution packages - client, manager + dev*

I've compiled and installed Wine and I've installed BOINCTasks 1.08 Beta (32 bit) after that. It seems to work without problems though I have to admit that my setup is rather simple (only one BOINC box).

*For my PG CUDA work although I build the 32 bit BOINC libs for the faster (than their 64 bit counterparts) 32 bit PG CUDA apps manually.
3) Message boards : Number crunching : GTX 560 Ti SoC not returning in 3D mode after restart of GPU task (Message 1109015)
Posted 23 May 2011 by Profile Microcruncher*
Post:
OK, I'm using the newest beta & skipped the 270.xx since I had to stay back at 266.58 for development until yesterday, so I'll take your word for it :)

The problem described here though, that is 'sticky downclock problem, on Boinc snooze or exit' apears to be a boincapi windows specific problem, rather than a driver one.

Jason

The problem occurred outside of BOINC too (GTX 470 / 270.61 WHQL drivers) as soon as the clocks were not set to their stock values (a.k.a overclocking). Pausing and resuming a CUDA 3.2 application was enough to lock the card into P2 mode (405/810 MHz). Rebooting was necessary to resume normal operation. 266.58 WHQL works without problems.
4) Message boards : Number crunching : Need a new machine on a small budget. (Message 1103791)
Posted 6 May 2011 by Profile Microcruncher*
Post:
the 470 has twice the CUDA-Cores as the 460.(6or7 vs 14, don't know)

The 460 has 7 MPs a 48 cores -> 336 cores (Compute capability 2.1).
The 470 has 14 MPs a 32 cores -> 448 cores (Compute capability 2.0).

The problem is that many CUDA apps lack the required instruction level parallelism (a.k.a. they are not optimized for CC 2.1 cards) to make efficient use of the 48 core MPs of the 460/560 cards.





 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.