Message boards : Graphics cards (GPUs) : BOINC 6.4.2 now avalible
Author | Message |
---|---|
New build: | |
ID: 4120 | Rating: 0 | rate: / Reply Quote | |
From an email I received earlier today about what is new in 6.4.2. | |
ID: 4121 | Rating: 0 | rate: / Reply Quote | |
If you upgrade, your current task (GPUgrid) might be in limbo as it did on 2 of my rigs. The rest of my rigs, i suspend first the gpugrid before upgrading then resume after the benchmark - works well by doing this. | |
ID: 4127 | Rating: 0 | rate: / Reply Quote | |
If this works well, we will suggest this release version. | |
ID: 4129 | Rating: 0 | rate: / Reply Quote | |
If this works well, we will suggest this release version. Testing is underway. | |
ID: 4130 | Rating: 0 | rate: / Reply Quote | |
Looks good and the Accessible View is back, only some refresh bugs in tabs, reported at boinc alpha. | |
ID: 4133 | Rating: 0 | rate: / Reply Quote | |
If this works well, we will suggest this release version. You should wait for 6.4.3. More small fixes/enhancements have been implemeted since 6.4.2 was released. They are working toward the goal of smoothing out work load, no more too few or too many for either cpu's or gpu's. Once a majority of users upgrade you can remove the X per cpu limit you now have set, which doens't work well for all users here. There already should be a new gpu limit in the server software. The client should better handle getting the correct number of tasks per gpu per computer and also adjust as with cpu jobs for the time (counted in flops) the gpu portion taks and not overload slower gpu's with work that cannot be finised by deadline. Faster gpu's will of course get more work on standby depending on queue size if it can be estiamted to be completed within deadline. You probably should also consider lowereing the 0.90 cpu use number to a more realistic numebr. I don't know if you can have separate for each o/s so use 0.35 which is around the windows usage. IF you can ahve separate then use the 0.02 for linux and 0.35 for windows. That way suers with multiple gpus will have a more closer cpu per gpu usage for the part boinc does the computations for. | |
ID: 4143 | Rating: 0 | rate: / Reply Quote | |
and 0.35 for windows If I give my GPU a dedicated core the usage is just below 20% of my Q6600@3GHz on average, which amounts to 80% of a core. Using the maximum number of cpu tasks drops this value to something between 15 and 20%. So 35% is not a general value.. and neither do I expect my 80% to be. MrS ____________ Scanning for our furry friends since Jan 2002 | |
ID: 4147 | Rating: 0 | rate: / Reply Quote | |
and 0.35 for windows Actually your right. The 35 is what one half of my HT CPU uses (more like 30-40 so I just picked a number in the middle, where 50 is the max, so it is more like 80% of a core and not the entire CPU. It's been a long work day, my brain is fried. | |
ID: 4149 | Rating: 0 | rate: / Reply Quote | |
If I give my GPU a dedicated core the usage is just below 20% of my Q6600@3GHz on average, which amounts to 80% of a core. Using the maximum number of cpu tasks drops this value to something between 15 and 20%. So 35% is not a general value.. and neither do I expect my 80% to be. On my GTX 260/Q9300 the acemd task needs about 14% CPU which would be 56% of one core if I run only three CPU tasks... I already reported that on the BOINC alpha mailing list some weeks ago before they meant that it is time to drop 6.3 and switch to 6.4 to bring out a CUDA BOINC client, but got ignored by the devs. The only answer I got was from JM7 - I'm a bit surprised that it is taking 60% of a CPU if there is a CPU that is completely free and only 10% of the CPU if there is a CPU intensive task running as I thought that the priority of the CPU portion of the GPU task was run at higher poriority than the CPU intensive tasks. In fact it is running with higher priority, but still it doesn't get the CPU it would need... But I don't see much sense anymore to report such things to BOINC alpha if you don't get an answer from the devs. Not a single question, no "we are looking into the problem". Nothing... :-/ I would have thought that this is an important thing if they want a working CUDA BOINC client. And they are really wondering why there are only so few alpha testers?! ____________ pixelicious.at - my little photoblog | |
ID: 4150 | Rating: 0 | rate: / Reply Quote | |
I can imagine they're busy with other stuff and regard this as a temporary issue, because it could change anytime the GPU client changes. Or they've got plenty of time until another GPU project appears and it's generally an issue of the specific app and the win scheduler, not so much BOINC. BOINC does start the GPU-task with higher priority.. what else could BOINC do anyway? An answer would be nice, though! In fact it is running with higher priority, but still it doesn't get the CPU it would need... Agreed, at least under win. MrS ____________ Scanning for our furry friends since Jan 2002 | |
ID: 4152 | Rating: 0 | rate: / Reply Quote | |
Message boards : Graphics cards (GPUs) : BOINC 6.4.2 now avalible