|
21)
Message boards :
Questions and problems :
Unintentional "Return Results Immediately"
(Message 39439)
Posted 4 Aug 2011 by Stick Post: Another example of immediate reporting: 8/4/2011 7:42:30 AM | SETI@home | Finished upload of 14mr11ab.692.21744.13.10.161_1_0 I think I've noticed another difference in the way v6.12.33 is operating as compared to earlier BOINC versions. That is, other versions of BOINC would have requested new work from Seti before the last task in cache had finished. BOINC v6.12.33 waited until the last task finished and uploaded - then it (immediately) requested new work and reported the completed task at the same time. (I looked at my event log for several hours prior to the above entries and verified that BOINC had not requested work from Seti during that time.) |
|
22)
Message boards :
Questions and problems :
Unintentional "Return Results Immediately"
(Message 39424)
Posted 3 Aug 2011 by Stick Post: I've never been quite sure how much of a deliberate BOINC development policy that was. Now that I think about it, I believe the one minute delay was a fix to one of Crunch3r's optimized BOINC clients (obviously, a long time ago). But, it was in response to an identified "reporting too early" problem. There's no sign of that in your log - are you sure that this scheduler request wasn't reporting a previous task? Yes, I am sure. Both Seti and Milkyway have had alot of "No work available" periods lately. And, I've seen this "immediate reporting" of the last task in cache on both projects. (Unfortunately, I've restarted since posting - so the logs are gone.) |
|
23)
Message boards :
Questions and problems :
Unintentional "Return Results Immediately"
(Message 39419)
Posted 2 Aug 2011 by Stick Post: I've noticed another aspect to the way v6.12.33 is reporting results without any delay. That is, when a project is out of work and my computer has finished the last task in cache from that project, my computer reports that task 0 to 3 seconds after it has finished uploading it (at the same time it requests new work). I've seen this happen with both Seti and Milkyway recently. Here's an example from Milkyway: 8/2/2011 6:54:28 PM | Milkyway@home | Computation for task ps_separation_10_3s_fix10_2_1459048_2 finished As I asked in the post below, shouldn't BOINC be using a one minute delay before reporting results? I know that, a few years ago, some results were being lost because they were being reported too soon and a one minute delay was implemented to fix that problem. Is the delay no longer necessary or does v6.12.33 need to be fixed? (I would note that, so far anyway, all my "early" reported results have been OK.) |
|
24)
Message boards :
Questions and problems :
Unintentional "Return Results Immediately"
(Message 39316)
Posted 27 Jul 2011 by Stick Post: There is a new feature in v6.12.33, that when a project is set to 'No new tasks' it is also, and automatically, set to report results immediately. Thanks Richard! I regularly use NNT and was not aware of the new feature in v6.12.33. But, what about the "one minute" delay? Is that not needed anymore? |
|
25)
Message boards :
Questions and problems :
Unintentional "Return Results Immediately"
(Message 39313)
Posted 27 Jul 2011 by Stick Post: I got a new notebook about a month ago and have 6.12.33(x64) running on it. Although I am a relatively experienced BOINC user, there are several aspects of this notebook's BOINC operation that are new to me. That is, it is my first computer with Windows 7, my first computer with a GPU and my first experience running BOINC 6.12.33. Therefore, I am not sure whether what I am about to describe is a BOINC "bug" or a BOINC "feature" combined with an "operator malfunction". My BOINC installation is returning results immediately - and when I say immediately, I mean IMMEDIATELY. That is, event logs indicate results are being reported one second after the upload is finished (as opposed to the one minute delay, I thought the feature was supposed to use). I did nothing (intentionally) to implement "report results immediately". Furthermore, it seems that this starts happening only after BOINC has been running for some time. That is, I have thought I have fixed the problem by restarting the computer, but - it starts doing it again eventually. Any thoughts and/or suggestions are welcome. |
|
26)
Message boards :
Projects :
SZTAKI Desktop Grid
(Message 29383)
Posted 11 Dec 2009 by Stick Post: Is it (hypothetically) possible? It it is, that's option that can be integrated to BOINC manager. The SZTAKI server was updated earlier this week - 64-bit CPU's can now get work. |
|
27)
Message boards :
Questions and problems :
6.6.38 problems
(Message 27949)
Posted 12 Oct 2009 by Stick Post: For you too, try BOINC 6.10.13. It's the release candidate for the 6.10 series. If it also has crashing problems, let me know and I'll notify the developers. Looks like 6.10.13 works like it should with SZTAKI - at least it did with this result. Here are the messages related to its upload: 10/12/2009 7:04:01 PM SZTAKI Desktop Grid Started upload of caa03215-1b38-489c-abd4-252c594ad6ff_6f4d3cfd-b2ab-4430-b46d-7f9eadb8435f_450036_2_0 |
|
28)
Message boards :
Questions and problems :
6.6.38 problems
(Message 27919)
Posted 12 Oct 2009 by Stick Post: . . . that was an annoyance. This problem causes 6.6.38 to crash. While that may not be enough for it to rate a "MAY BE UNSTABLE" label, in my book, the "Recommended" rating is questionable. As I tried to say earlier, if the 6.6.38 problem is now isolated to SZTAKI, I agree with you. But, having experienced the "calculations enabled 100% of that" problem with 6.6.36, I still think that "annoyance" is an apt descriptor. The point is, neither problem is something that should be in a "recommended" release. (And, in that regard, maybe 5.10.45 was better.) ;-) For you too, try BOINC 6.10.13. It's the release candidate for the 6.10 series. If it also has crashing problems, let me know and I'll notify the developers. I'll do it sometime soon (with SZTAKI) and report back. But until that time, there is some responsibility for the Projects as well to keep their server software up-to-date, so try bombarding the admin there with requests to get the 2 year old server software updated. Knowing what I do about the admins/devs at SZTAKI, I am surprised to hear their software is only 2 years out of date. ;-) But I'll do what I can to prod them and also to warn SZTAKI users against upgrading to 6.6.38. |
|
29)
Message boards :
Questions and problems :
6.6.38 problems
(Message 27901)
Posted 12 Oct 2009 by Stick Post: (*) I see that the Lattice project has just updated their server software. If that means SZTAKI is the lone hold-out, then I agree. But . . . 6.6.36 has a problem where the scheduler will eventually answer that your work request cannot go through, as your BOINC is on for so much percent, with calculation enabled 100%. 6.6.38 has a fix for that on the client side.. . . that was an annoyance. This problem causes 6.6.38 to crash. While that may not be enough for it to rate a "MAY BE UNSTABLE" label, in my book, the "Recommended" rating is questionable. You could just as well revert back to BOINC 5.10.45 then and say that's better off made recommended. When I started with BOINC, I think the recommended version was 4.06. And, I generally upgrade when a new recommended version is released. Having done that, I have seen a lot of improvements to the program and also a lot of minor glitches. 5.10.45 had glitches and so does 6.6.36. Progress isn't always smooth. But I had come to expect a level of stability with the BOINC "recommended version" that 6.6.38 just didn't live up to. That is why I finally joined the BOINC forum and made my report. |
|
30)
Message boards :
Questions and problems :
6.6.38 problems
(Message 27890)
Posted 11 Oct 2009 by Stick Post: Another instance of the problem with SZTAKI posted here. So I tend to agree with the comment below - 6.6.38 should not be the recommended version. I would also note that the BOINC version history page does not yet acknowledge the existence of 6.6.38. The main problem I see with this is that 6.6.38 is the default/recommended BOINC client to download and that is the version that crashes. Some people running Lattice are getting frustrated and canceling WU's or dropping Lattice because of this. |
|
31)
Message boards :
Questions and problems :
local host disconnect
(Message 27865)
Posted 10 Oct 2009 by Stick Post: hi i am a boinc user since about 3 years and yesterday my boinc manager cant connect to a client, my local host is disconnected. i try delete and reinstall boinc 6.6.38 , i try the looking to the firewall and it still not working. i am on window xp what can i do to make it work again. please make it simple if possible because i am speaking french, i understand english but not all. thanks Could be the same problem I reported here. You might try going back to an earlier BOINC version. |
|
32)
Message boards :
Questions and problems :
6.6.38 problems
(Message 27859)
Posted 10 Oct 2009 by Stick Post: I had problems uploading these SZTAKI results with 6.6.38: http://szdg.lpds.sztaki.hu/szdg/result.php?resultid=10415951 http://szdg.lpds.sztaki.hu/szdg/result.php?resultid=10417381 SZTAKI results generate several files for upload - one of which is apparently empty (i.e zero bytes) and I believe the problem occurred when BOINC attempted to upload the empty file. When this happened, the BOINC client disconnected from BOINC manager. All attempts to reconnect failed - including BOINC restarts and BOINC "repair" installations. But, reverting back to 6.6.36 fixed it. Note that I had the same problem with both my laptop and desktop computers. |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.