Currently 70k credit long-runs take John 33k seconds, running 2 of them might require ~60 ks. The GTX650Ti (Johns GPUs) sounds like it's almost the same as a GTX660Ti (Jacobs GPUs), but it's actually about a factor of 2 slower. A machine reboot or GPU error (or as Jacob pointed out on the BOINC list, a BOINC restart) would be more likely to take out 2 of these long WUs instead of 1.Ĭareful, guys. As an aside I think running GPUGrid WUs 2x is a bad idea due to longer turn around time and possible errors. A real workaround would be to run the 2x WUs on a box with 1 NV and 1 ATI running on a different project, then 4 WUs would be allocated for the machine. To clarify, a simple example: a machine with 1 GPU would get 2 WUs and if these are not in sync, then while uploading/downloading 1 WU the other WU would run at 2x the speed. Having more GPUs & WUs in flight should help with this issue. Depending on your upload speed this might provide enough overlap to avoid running dry. Point 1: ideally this would average out after some time, so that the different WUs per GPU finish at different times. I'll continue using this "2-at-a-time" approach, and will reply here if I find anything different. Now, admittedly, I am estimating on very few results here, but. So far, it looks like running multiple tasks at a time. Running at 0.001, 0.5, BOINC set at 100% processors, along with a full load of other GPU/CPU tasks: Note: The GPU Load goes to ~97% when I do this, and I believe that's a good thing! But I wanted to find out what would happen when I run 2. So, previously, I was only running 1 GPU Task on that GPU (and the GPU Load would usually be around 87%-88%). So, again, as expected, there is only slight contention while under full CPU load, because the ACEMD process actually runs at a higher priority than other BOINC task processes, and therefor, are never starved for CPU, and are likely only minorly starved for contention during CPU process context switching. Here are some more results, where I focused on the "short" Nathan units: It's not affected much because the ACEMD process actually runs at a higher priority than other BOINC task processes, and therefor, are never starved for CPU, and are likely only minorly starved for contention during CPU process context switching. So, as expected, there is some minor CPU contention whilst under full load, but not much (Task Run time is maybe ~3% slower). Running at 0.001, BOINC set at 100% processors, along with a full load of other GPU/CPU tasks: Running with no other tasks (every other BOINC task and project was suspended, so the single GPUGrid task was free to use up the whole CPU core): Here are the first results (from running only on my GTX 660 Ti), copied from that thread:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |