Message boards : Graphics cards (GPUs) : New BOINC client 6.6.3 for testing.
Author | Message |
---|---|
The following fixes are included in this BOINC client software version released earlier today for testing... | |
ID: 6150 | Rating: 0 | rate: / Reply Quote | |
Has anyone tired it? | |
ID: 6156 | Rating: 0 | rate: / Reply Quote | |
Has anyone tired it? http://www.gpugrid.net/forum_thread.php?id=684&nowrap=true#6154 | |
ID: 6158 | Rating: 0 | rate: / Reply Quote | |
Just installed it on Vista x64 + 2x 8800GS--It aborted all current tasks (WCG and GPUGrid) and re-DLed new ones. Currently it has only DLed 2x GPUGrid WUs--it has always been 4x WUs in every previous version. Cpu usage is 0-2%. | |
ID: 6165 | Rating: 0 | rate: / Reply Quote | |
I installed BOINC 6.6.3 on two home computers last night and no significant problems so far, though I did see something similar to naja's, where I tried to fetch GPUGrid work and didn't the first time, but forced a second update and it did get some work. | |
ID: 6168 | Rating: 0 | rate: / Reply Quote | |
Yesterday I upgraded BOINC 6.4.5 to 6.6.3 without any problems on an Intel Quad Q6600 with WinXP SP3. | |
ID: 6169 | Rating: 0 | rate: / Reply Quote | |
I installed BOINC 6.6.3 on two home computers last night and no significant problems so far, though I did see something similar to naja's, where I tried to fetch GPUGrid work and didn't the first time, but forced a second update and it did get some work. Agreed, Mine has picked up 2 more WUs since my last post. Cpu usage is still the same 0-2%. So far everything seems good, except losing all of the work and WUs during the change-over.... | |
ID: 6174 | Rating: 0 | rate: / Reply Quote | |
Just installed 6.6.3 into another rig. It did not abort the WUs, etc. Started up, benchmarked and went to work--NP. But this machine is coming from 6.3.21, so I would say that's the difference. | |
ID: 6175 | Rating: 0 | rate: / Reply Quote | |
So far everything seems good, except losing all of the work and WUs during the change-over.... I upgraded about 6 hours ago on both machines with no problems so far. I've had problems with the installer not stopping the GPU task cleanly in the past so I suspended all activity before running the installer. I let the installer shut down the boinc client and the boinc manager though. I didn't loose any work units doing it that way, but then I am using the Win 32 bit variant and you are on the Win 64 bit. Phoneman1 | |
ID: 6176 | Rating: 0 | rate: / Reply Quote | |
So far everything seems good, except losing all of the work and WUs during the change-over.... I lost all WUs when I went to 6.4.2 or 6.4.5 (I think I installed 6.4.2 on both though). I switched the 1 rig back to 6.3.21 and the other to 6.4.5. Today when I switched from 6.4.5-I lost all WUs, but not switching from 6.3.21. Going into 6.4.? I lost all WUs and coming out of it--same thing. | |
ID: 6177 | Rating: 0 | rate: / Reply Quote | |
It can't seem to download any WU. | |
ID: 6178 | Rating: 0 | rate: / Reply Quote | |
I lost all WUs when I went to 6.4.2 or 6.4.5 (I think I installed 6.4.2 on both though). I switched the 1 rig back to 6.3.21 and the other to 6.4.5. Today when I switched from 6.4.5-I lost all WUs, but not switching from 6.3.21. Interesting, I wonder why this is happening to you? I've switched many times between various versions of BOINC 6.xx (both forward & backward & even 5.xx & including 6.4.1, 6.4.2, 6.4.5, 6.3.21) and have never lost any WUs in any project. | |
ID: 6180 | Rating: 0 | rate: / Reply Quote | |
I've switched many times between various versions of BOINC 6.xx (both forward & backward & even 5.xx & including 6.4.1, 6.4.2, 6.4.5, 6.3.21) and have never lost any WUs in any project. The loss of GPUgrid Wu's has been a hit or miss thing with many people. It depends on OS, Client, how you shutdown the client, upgrading or downgrading etc. Many have not been 'Bit' by this, some have... I try to suspend "non-running" Wu's and run down my "Active Wu's" just in case, then upgrade. I hate losing 'half crunched' Wu's....in the name of science... ____________ Consciousness: That annoying time between naps...... Experience is a wonderful thing: it enables you to recognize a mistake every time you repeat it. | |
ID: 6185 | Rating: 0 | rate: / Reply Quote | |
Everything is OK with WUs during upgrade, as usually. But it doesn't request work for gpugrid automatically! I am forced to make it by my hands again!!! Aggghhhrrrrr.... Is it so difficult for NORMAL programmer to fix this bug?! | |
ID: 6203 | Rating: 0 | rate: / Reply Quote | |
Everything is OK with WUs during upgrade, as usually. But it doesn't request work for gpugrid automatically! I am forced to make it by my hands again!!! Aggghhhrrrrr.... Is it so difficult for NORMAL programmer to fix this bug?! Well, the good news is that there was only one major bug in 6.6.3 in calculating LTD ... which may very well mean that you will have trouble getting work ... :) were it me, I would down level again until 6.6.4 ... | |
ID: 6206 | Rating: 0 | rate: / Reply Quote | |
Has anyone tired it? Yes, I tired... Tired of waiting for NORMAL version of BOINC, which could automatically get work for gpugrid (CUDA s@h, CUDA e@h in future)... :-) ____________ From Siberia with love! | |
ID: 6207 | Rating: 0 | rate: / Reply Quote | |
I couldn't get any new work GPU units on 2 different Box's using 6.6.3 ... | |
ID: 6208 | Rating: 0 | rate: / Reply Quote | |
The 6.6.3 is running fine , but there are some changes I don't like. I can't see the amount of called work and had on one PC the situation, that he crunched all WUs and would not call new work 'til the last WU had less than 2 hours to work. | |
ID: 6209 | Rating: 0 | rate: / Reply Quote | |
According to Boincview GPU's LTD is now zero on both of my machines. My other project, Cosmology, shows -4.8 million on one and -11.2 million on the other. It does not seem to have afftected getting work for either project. On both machines 1 GPU is running and 2 are queued ready. Three of those queued were downloaded today, I upgraded to 6.6.3 this time yesterday. There are 4 Cosmology tasks running on each machine and the normal number (half a day's worth) queued ready to run. I'm going to stop Boinc and reset all the LTDs to zero and see what happens. I think the fact that GPU LTD is zero now is by design and not a bug. I am not sure what it would be if I was running another GPU project. It looks to me like they are separating the work fetch mechanisms for CPU and GPU type projects. Phoneman1 | |
ID: 6210 | Rating: 0 | rate: / Reply Quote | |
I think the fact that GPU LTD is zero now is by design and not a bug. I am not sure what it would be if I was running another GPU project. It looks to me like they are separating the work fetch mechanisms for CPU and GPU type projects. Yes, that is the intent. Also making minor changes for non-CPU projects ... If you are attached to lots of projects JM VII found issues that indicate that you can run dry of work with 6.6.3 ... YMMV | |
ID: 6211 | Rating: 0 | rate: / Reply Quote | |
I think the fact that GPU LTD is zero now is by design and not a bug. I am not sure what it would be if I was running another GPU project. It looks to me like they are separating the work fetch mechanisms for CPU and GPU type projects. I had to go back to v6.3.21 because 6.6.3 Wouldn't give me any more GPU WU's no matter what I did. I tried 6.4.5 but that Version would let me run 4&1 on a Quad or 8&2 on my i7. Version 6.3.21 is the only Version so far that gives me more GPU Work & lets me run 4&1 and 8&2 ... | |
ID: 6212 | Rating: 0 | rate: / Reply Quote | |
SAME PROBLEMS HERE! | |
ID: 6215 | Rating: 0 | rate: / Reply Quote | |
SAME PROBLEMS HERE! Is this a problem with the x64 variant - I wonder.... Anyone having problems getting GPU tasks on Win 32 bit or Linux 32 bit with 6.6.3??? Phoneman1 | |
ID: 6217 | Rating: 0 | rate: / Reply Quote | |
Version 6.3.21 is the only Version so far that gives me more GPU Work & lets me run 4&1 and 8&2 ... Did you try 6.5.0? I found it to be surprisingly well-behaved. MrS ____________ Scanning for our furry friends since Jan 2002 | |
ID: 6220 | Rating: 0 | rate: / Reply Quote | |
Anyone having problems getting GPU tasks on Win 32 bit or Linux 32 bit with 6.6.3??? No probs so far with WinXP 32 bit (BOINC 6.6.3 installed two days ago). | |
ID: 6221 | Rating: 0 | rate: / Reply Quote | |
I am experiencing GPUGrid work fetch problems under BOINC client 6.6.3 after upgrading several days ago. I have run out of work and with repeated attempts to get work manually including resetting the project without success. | |
ID: 6222 | Rating: 0 | rate: / Reply Quote | |
There is a major bug in 6.6.3 which Dr. Anderson fixed related to the calculation of LTD. There are varying and different problems with all the 6.6.x versions from dot zero to dot three ... | |
ID: 6225 | Rating: 0 | rate: / Reply Quote | |
Thanks Paul. | |
ID: 6226 | Rating: 0 | rate: / Reply Quote | |
Works ok for me on two machines, vista64 and xp32; no problems | |
ID: 6227 | Rating: 0 | rate: / Reply Quote | |
I just had to downgrade from 6.6.3 because it fetched way too much WUs of a CPU intense project. :-( | |
ID: 6230 | Rating: 0 | rate: / Reply Quote | |
I thought it was OK at first also. But there was no way I could get more work to fill the queue. | |
ID: 6232 | Rating: 0 | rate: / Reply Quote | |
Just a quick up date: No problems here. 2 rigs: Vista 64 3x 8800GS (total). Unless something changes....I'm going to stick with this for a while.... | |
ID: 6236 | Rating: 0 | rate: / Reply Quote | |
Initialization problems in code are usually the hardest to find because the system under many conditions can appear to be running correctly. In this case, the testing variable is not set with the initial value of the first project as the scanning loop begins. Now, it is entirely possible that the value that the variable has at the beginning of the loop is "close" enough so that it will do a proper scan ... but in other cases the first project in the list should be the value in the testing variable ... and it is never set ... | |
ID: 6238 | Rating: 0 | rate: / Reply Quote | |
Initialization problems in code are usually the hardest to find because the system under many conditions can appear to be running correctly. In this case, the testing variable is not set with the initial value of the first project as the scanning loop begins. Now, it is entirely possible that the value that the variable has at the beginning of the loop is "close" enough so that it will do a proper scan ... but in other cases the first project in the list should be the value in the testing variable ... and it is never set ... I don't recall you mentioning the initialize issue on the mailing list. Do you have a snippet of code you could provide where you think the issue is, or is that the LTD fix Dr A has done? It seems the suspend/resume buttons is the only fix so far in 6.6.4. The fact they didn't want to build a new version suggests they may be aware of more bugs and want to include (or are working on) fixes for them. Or maybe they just want to give us the weekend to give 6.6.3 a shake down. ____________ BOINC blog | |
ID: 6241 | Rating: 0 | rate: / Reply Quote | |
Initialization problems in code are usually the hardest to find because the system under many conditions can appear to be running correctly. Absolutely. This version looked good for most of yesterday and the day before on my systems. On my final check of yesterday evening it hadn't replaced a completed GPU task but was running one with one in the queue - plenty of time to sort itself out I thought - Wrong! I've just checked for the first time today and found the last GPU task had ended nearly 2 hours before and no request for work had been made. A manual update did not request any work so I suspended the other project and tried again. That brought two GPU tasks, it then automically asked for more work and got two more. Then again but this time it was refused because I had reached 1 per core! Clearly 6.6.3 is not to be trusted even on Win 32 so I've gone back to 6.5.0. Phoneman1 | |
ID: 6245 | Rating: 0 | rate: / Reply Quote | |
I don't recall you mentioning the initialize issue on the mailing list. Do you have a snippet of code you could provide where you think the issue is, or is that the LTD fix Dr A has done? The one Dr. Anderson found. However, I did look at the code change he made and in essence the first project visited should have its value stored in the scan variable. It isn't... Assuming C does initialize the value to zero, the scan value starts with this position to begin to discover the project with the largest value. If the first project has this value, it will never be discovered. Thus, after a few days, the first project in the list will inevitably become the project with the largest value but this will not be established ... with that ... you get issues ... now I did not look at the whole set of code ... but so far I cannot recall anyone that has run 6.6.3 that has not back-leveled after a couple of days ... Not putting up another version can suggest or imply what you said. However, this bug is so severe that you cannot use this version for testing at all ... thus you cannot check the operation of 6.6.3 and contrast it with the versions that came before ... it is too severely damaged for that ... | |
ID: 6250 | Rating: 0 | rate: / Reply Quote | |
The one Dr. Anderson found. However, I did look at the code change he made and in essence the first project visited should have its value stored in the scan variable. It isn't... Assuming C does initialize the value to zero, the scan value starts with this position to begin to discover the project with the largest value. If the first project has this value, it will never be discovered. I have 6.6.3 on three machines (non-cuda), but i'm sticking with 6.5.0 on the one cuda-capable machine for the time being. I will take the non-cuda ones back to 6.2.19. There are a few reports of work-fetch issues popping up in boinc_alpha with the debug logging so there is a fair bit of information there for the guys to examine. I don't know if you subscribe to it or just boinc_dev? Maybe you should mention your concern with the code change. ____________ BOINC blog | |
ID: 6287 | Rating: 0 | rate: / Reply Quote | |
There are a few reports of work-fetch issues popping up in boinc_alpha with the debug logging so there is a fair bit of information there for the guys to examine. I don't know if you subscribe to it or just boinc_dev? Maybe you should mention your concern with the code change. BOINC Dev and Projects ... I don't have a concern with the CHANGE ... just with the lack of 6.6.4 with the code change in it ... Dr. Anderson suggested that if we wanted it we could compile our own ... which is not a really viable suggestion for most. Personally as a developer (past life) I find it a poor judgement that they would leave a version up for download with such a devastatingly subtle bug in it for people to download ... And firing off a build in the background on their PCs that are set-up for it is not that difficult ... | |
ID: 6297 | Rating: 0 | rate: / Reply Quote | |
.. just don't forget that these are developer versions, not even alphas. Personally I'm not that keen on testing these new versions, as most of the time something is quite broken. | |
ID: 6358 | Rating: 0 | rate: / Reply Quote | |
Message boards : Graphics cards (GPUs) : New BOINC client 6.6.3 for testing.