11) Message boards : Graphics cards (GPUs) : APP names (Message 26057)
Posted 4327 days ago by Profile K1atOdessa
BOINC can do this for you without any special script. Use "exclude_gpu" option in the cc_config.xml file, such as below:

<cc_config>
<options>
<report_results_immediately>1</report_results_immediately>
<use_all_gpus>1</use_all_gpus>


<!-- ======= SETUP GPU 0: (Use GPUGrid, not SETI) ======= -->
<exclude_gpu>
<url>http://setiathome.berkeley.edu/</url>
<device_num>0</device_num>
</exclude_gpu>


<!-- ======= SETUP GPU 1: (Use SETI, not GPUGrid) ======= -->
<exclude_gpu>
<url>http://www.gpugrid.net/</url>
<device_num>1</device_num>
</exclude_gpu>

</options>
</cc_config>


You can add as many exclusions as you want. Any project you've set options to get CUDA work will process on GPU0 except for SETI, and likewise for GPU1 except for GPUGrid. So, let's assume you also don't want Primegrid to run on GPU0 (dedicated just for GPUGrid) -- then you just use the same format but put in PrimeGrid's URL.
12) Message boards : Number crunching : Workaround for the "CUDA3.1 client sent to CUDA4.2 capable hosts" problem (Message 25984)
Posted 4329 days ago by Profile K1atOdessa
Looks like after a system reboot, the old cuda3.1 executable is downloaded again. So, it appears the batch file needs to be run after every reboot.


6/28/2012 10:42:30 PM | GPUGRID | Started download of acemd.win.2352
13) Message boards : Number crunching : Workaround for the "CUDA3.1 client sent to CUDA4.2 capable hosts" problem (Message 25951)
Posted 4330 days ago by Profile K1atOdessa
I think I've had a cuda3.1 download after a cuda4.2, without an "error while downloading".


OK. On my second system, I definitely just had this scenario. No issues and it is 20 minutes in.

One interesting thing is that the slot appears to have changed from 8 (this afternoon) to 9 (right now). Looking into the slot 9 folder, it definitely has the cuda4.2 file size renamed as the cuda3.1 filename. However, it has the cuda3.2 .dll files (no sign of the cuda4.2 dll's).

This doesn't seem to impact the WU running (its been plugging along for 20+ minutes now), but not sure why I don't see the cuda4.2 dll's. Speed seems on par for the cuda4.2 WU's.

I'm not an expert, so does it makes sense that the cuda4.2 executable can run with the cuda3.1 dll's?
14) Message boards : Number crunching : Workaround for the "CUDA3.1 client sent to CUDA4.2 capable hosts" problem (Message 25949)
Posted 4330 days ago by Profile K1atOdessa
I have a different problem with the scheduling of this batch program:
When a new CUDA3.1 task is downloaded, it is receive an "error while downloading".
I couldn't catch it while it happened, I will keep an eye on it.


I think I've had a cuda3.1 download after a cuda4.2, without an "error while downloading". I'll let your batch run for 24 hours and see what other errors it generates. So far, having a single WU error out immediately while running a cuda3.1 WU in only 60% of the time (with another well on its way to completion) has been worth the effort.

Definitely interesting way to try to solve the issue, though probably not the silver bullet a separate queue selection would be.
15) Message boards : Number crunching : Workaround for the "CUDA3.1 client sent to CUDA4.2 capable hosts" problem (Message 25942)
Posted 4331 days ago by Profile K1atOdessa
I tried your batch files. Seemed to run fine on the running task (cuda3.1) and made it run like a cuda4.2.

After that task ended, the next task was a cuda4.2 and errored out immediately.

Task Error

However, once the error task uploaded, I got another cuda4.2 task crunching fine. Who knows if it was just some weird issue.
16) Message boards : Number crunching : Workaround for the "CUDA3.1 client sent to CUDA4.2 capable hosts" problem (Message 25926)
Posted 4331 days ago by Profile K1atOdessa
Am I correct in that you need to do this every time you notice a cuda3.1 WU running?

Very cool that this appears to work, but quite a bit of monitoring of the system.
17) Message boards : News : New CUDA4.2 applications are out for Kepler GPUs (Message 25905)
Posted 4332 days ago by Profile K1atOdessa
I would suggest making the long queue CUDA 4.2 only, but I'm not sure how many people have a suitable driver, how many don't, and of those that don't have compatible drivers for CUDA4.2 how many run normal length tasks or both normal and long?


As was suggested before, maybe a solution is to have 2 long queues selectable in the preferences: 1 for cuda3.1 long and 1 for cuda4.2 long? Not sure if that is easy/possible, but I know if I could deselect the cuda3.1 long and only select the cuda4.2 long, that'd be great for me. For those that want both or only cuda3.1 long, it still allows full flexibility.
18) Message boards : News : New CUDA4.2 applications are out for Kepler GPUs (Message 25898)
Posted 4332 days ago by Profile K1atOdessa
You have 301.42, and did get a 4.2 task after resetting, so why the 3.1?
I see you have a GT240 (CC 1.2) in one system, but that would not explain the other getting 3.1 tasks (unless a GT440 is deemed as being too slow)?

Which card is the 3.1 task running on?


I have two systems:

A: 1x GTX570 (GPUGrid only) and 1x GT440 (non-GPUGrid, only PrimeGrid, etc.)
B: 1x GTX570 (GPUGrid only) and 3x GT240 (non-GPUGrid, only PrimeGrid, etc.)


I use the cc_config.xml options to specify which projects get which cards. I devote the 570's to GPUGrid (since I started with you guys), and have merely demoted old GPUGrid cards to other projects that accept them.


I am OK getting a mix of cuda4.2 and cuda3.1 tasks, though I hope I don't get ONLY cuda3.1 tasks now, unless I do a reset project. I'd love the 30%+ credit bonus, and I'm sure GPUGrid would love the 30%+ throughput increase from Fermi/Kepler cards. If you guys can identify the server issue (or whatever it is), I think it'll be a win/win.

But, for now, I'm happy to continue with the cuda3.2's with the hopes a nice cuda4.2 strolls down my street. :-)
19) Message boards : News : New CUDA4.2 applications are out for Kepler GPUs (Message 25894)
Posted 4332 days ago by Profile K1atOdessa

Anyone wishing to exclusively run CUDA 4.2 tasks (ie not 3.1 and 4.2)?
I suggest people select no new tasks, finish any tasks in progress and then reset the project. This will delete the 3.1 App. If you reset while you have a task, and are running it on 3.1, it's probably going to start running it again and fail.


Doesn't seem like that is a permanent solution. I did that and after receiving 2-3 cuda4.2 WU's, it went back to grabbing a cuda3.1 without intervention.

6/26/2012 9:00:34 AM | GPUGRID | Sending scheduler request: To fetch work.
6/26/2012 9:00:34 AM | GPUGRID | Requesting new tasks for NVIDIA
6/26/2012 9:00:37 AM | GPUGRID | Scheduler request completed: got 1 new tasks
6/26/2012 9:00:39 AM | GPUGRID | Started download of acemd.win.2352
6/26/2012 9:00:39 AM | GPUGRID | Started download of cudart32_31_9.dll
6/26/2012 9:00:42 AM | GPUGRID | Finished download of cudart32_31_9.dll
6/26/2012 9:00:42 AM | GPUGRID | Started download of cufft32_31_9.dll
6/26/2012 9:00:49 AM | GPUGRID | Finished download of acemd.win.2352
6/26/2012 9:00:49 AM | GPUGRID | Started download of I2R137-NATHAN_RPS1120528-12-LICENSE
6/26/2012 9:00:50 AM | GPUGRID | Finished download of I2R137-NATHAN_RPS1120528-12-LICENSE
6/26/2012 9:00:50 AM | GPUGRID | Started download of I2R137-NATHAN_RPS1120528-12-COPYRIGHT
6/26/2012 9:00:51 AM | GPUGRID | Finished download of I2R137-NATHAN_RPS1120528-12-COPYRIGHT
6/26/2012 9:00:51 AM | GPUGRID | Started download of I2R137-NATHAN_RPS1120528-12-I2R137-NATHAN_RPS1120528-11-166-RND7611_1
6/26/2012 9:00:59 AM | GPUGRID | Finished download of I2R137-NATHAN_RPS1120528-12-I2R137-NATHAN_RPS1120528-11-166-RND7611_1
6/26/2012 9:00:59 AM | GPUGRID | Started download of I2R137-NATHAN_RPS1120528-12-I2R137-NATHAN_RPS1120528-11-166-RND7611_2
6/26/2012 9:01:06 AM | GPUGRID | Finished download of I2R137-NATHAN_RPS1120528-12-I2R137-NATHAN_RPS1120528-11-166-RND7611_2
6/26/2012 9:01:06 AM | GPUGRID | Started download of I2R137-NATHAN_RPS1120528-12-I2R137-NATHAN_RPS1120528-11-166-RND7611_3
6/26/2012 9:01:11 AM | GPUGRID | Finished download of I2R137-NATHAN_RPS1120528-12-I2R137-NATHAN_RPS1120528-11-166-RND7611_3
6/26/2012 9:01:11 AM | GPUGRID | Started download of I2R137-NATHAN_RPS1120528-12-pdb_file
6/26/2012 9:01:33 AM | GPUGRID | Finished download of I2R137-NATHAN_RPS1120528-12-pdb_file
6/26/2012 9:01:33 AM | GPUGRID | Started download of I2R137-NATHAN_RPS1120528-12-psf_file
6/26/2012 9:01:54 AM | GPUGRID | Finished download of cufft32_31_9.dll
6/26/2012 9:01:54 AM | GPUGRID | Started download of I2R137-NATHAN_RPS1120528-12-par_file
6/26/2012 9:01:58 AM | GPUGRID | Finished download of I2R137-NATHAN_RPS1120528-12-par_file
6/26/2012 9:01:58 AM | GPUGRID | Started download of I2R137-NATHAN_RPS1120528-12-conf_file_enc
6/26/2012 9:01:59 AM | GPUGRID | Finished download of I2R137-NATHAN_RPS1120528-12-conf_file_enc
6/26/2012 9:01:59 AM | GPUGRID | Started download of I2R137-NATHAN_RPS1120528-12-metainp_file
6/26/2012 9:02:00 AM | GPUGRID | Finished download of I2R137-NATHAN_RPS1120528-12-metainp_file
6/26/2012 9:02:00 AM | GPUGRID | Started download of I2R137-NATHAN_RPS1120528-12-I2R137-NATHAN_RPS1120528-11-166-RND7611_7
6/26/2012 9:02:01 AM | GPUGRID | Finished download of I2R137-NATHAN_RPS1120528-12-I2R137-NATHAN_RPS1120528-11-166-RND7611_7
6/26/2012 9:02:20 AM | GPUGRID | Finished download of I2R137-NATHAN_RPS1120528-12-psf_file
6/26/2012 9:02:21 AM | GPUGRID | Starting task I2R137-NATHAN_RPS1120528-12-166-RND7611_0 using acemdlong version 616 (cuda31) in slot 3
20) Message boards : News : New CUDA4.2 applications are out for Kepler GPUs (Message 25892)
Posted 4332 days ago by Profile K1atOdessa
I will let that run and see if I get any more cuda3.1 WU's.

Well, crap. After the "reset project" in BOINC, I did get through several long cuda4.2 WU's before getting another cuda3.1 WU. So, seems like it is luck of the draw right now.



This problem of receiving multiple applications is probably a bug of the server.
I am going to investigate it with Boinc people or maybe do a server upgrade.

For now, you have to live with it. Sorry.

gdf

Well, sporadic cuda4.2 is better than no cuda4.2 at all. :-) Please do look into the potential server issues sending out both types of WU's to a cuda4.2-eligible machine.


Previous 10 | Next 10
//