Posts by Ross

21) Message boards : Questions and problems : BOINC 6.10.58 released to public (Message 34151)
Posted 12 Aug 2010 by Ross
Post:
I would like to install the current version of BOINC. I am currently running 6.10.56, so it shouldn't be a big deal.

I would like to make one change, however. I would like to see BOINC from any user on the computer and be able to log out of all of them w/o closing down BOINC.

I'm also a little spooked by the many Work Units I have for SETI, which have not been uploaded or reported, during the mid-week time their servers are re-purposed for internal use.

I'm sure there's a FAQ or so around here, I'm just not aware of where it is. So, I don't think I'll need hand-holding to do the upgrade, just point me at where in the docs these issues are discussed.

Thanks.

Ross
22) Message boards : Projects : News on project outages (Message 33272)
Posted 5 Jun 2010 by Ross
Post:
I got a strange message in BOINC when I updated SETI. I had two completed WU and nothing SETI to run. When I did the Update:

6/5/2010 10:34:58 AM SETI@home update requested by user
6/5/2010 10:35:02 AM SETI@home Sending scheduler request: Requested by user.
6/5/2010 10:35:02 AM SETI@home Reporting 2 completed tasks, not requesting new tasks
6/5/2010 10:35:03 AM SETI@home Scheduler request completed
6/5/2010 11:17:23 AM SETI@home Sending scheduler request: To fetch work.
6/5/2010 11:17:23 AM SETI@home Requesting new tasks
6/5/2010 11:17:25 AM SETI@home Scheduler request completed: got 0 new tasks
6/5/2010 11:17:25 AM SETI@home Message from server: (Project has no jobs available)

As you see, at 10:34, it reported, at my request, but did not request new tasks. At 11:17, on its own, it requested work, w/o success, as noted elsewhere here. What I find puzzling is that at 10:35, BOINC did not request new tasks. Is requesting new tasks not something done for a manual update? Did BOINC wait until 11:17, when it would normally have switched over from Rosetta to SETI to make the request? I just now forced an update on Rosetta and it reported 1 completed task and did not request new tasks, so that's probably it.
23) Message boards : Questions and problems : Multiple WU progress toward completion (Message 33125)
Posted 30 May 2010 by Ross
Post:
LB, the original reason I went w/ Rosetta was to get past the weekly outages of SETI. I've tried to be even-handed in dealing with them (locally) and Rosetta has had some outages as well, but SETI seems to be in a sort of crisis, with all sorts of problems with servers, work generation, output queues, and more than I can remember. Even setiweb.ssl.berkeley.edu is down just now. It would appear to my distant eye that more folks are willing to contribute cycles than dollars. Even in the best of times they seem to be hanging by a slender thread above the fires of Hell. And if anything goes wrong goes wrong goes wrong xxxxxx, the whole world backs up trying to get in.
24) Message boards : Questions and problems : Multiple WU progress toward completion (Message 33123)
Posted 30 May 2010 by Ross
Post:
The Rosetta WU due 6/4/2010 10:28 PM is complete. Now the Rosetta WU due 6/4/2010 5:47 PM is Running, high priority with 23 hrs remaining. The Rosetta WU due 6/1/2010 is 79% complete with 7 hrs (estimated) remaining. I suppose it might finish in time, but the Rosetta WU due 6/2/2010 has an estimated 29 hrs processing and by all appearances, will precede the 6/1/2010 WU.

SETI is progressing normally, albeit, I'm only obtaining 1 WU at a time, and that after the previous one completes.

Perhaps the solution is to eliminate my requested backlog of 4 days. It's not working for SETI and it's counter-productive for Rosetta.
25) Message boards : Questions and problems : Multiple WU progress toward completion (Message 33088)
Posted 28 May 2010 by Ross
Post:
I'm posting here because I'm certain that this is a scheduling issue, not a computation issue. I have d/l and am running BOINC 6.10.56.

I am computing for both SETI and Rosetta. I currently have 4 Rosetta WU and 1 SETI WU. Despite my request for 4 days backlog of WU, SETI is dribbling them out one at a time after the previous one finishes. But that's a SETI problem.

My 4 Rosetta WU have stats: (Elapsed HH:MM, Completion, To Do HH:MM, Due date)
15:44, 50%, 14:40, 6/1/2010
---, 0%, 26:09, 6/2/2010
---, 0%, 26:09, 6/4/2010, 5:47 PM
11:57, 27%, 25:11, 6/4/2010, 10:28 PM Running, high priority
SETI:
2:34, 37%, 3:59, 7/14/2010

I have had NO problems with the SETI WU scheduling. OTOH, I'm currently getting only one at a time, so my recent experience with it is of limited value. But once again, BOINC is scheduling the most distant Rosetta WU, at high priority, yet. 6/1 is only 5 days off, so I could easily miss the deadline, if my compute time is squandered on later due WU. I guess I should take a look on Saturday or Sunday.

I'm not sure what form to follow for a trouble report, but this is certainly one.

Ross Parlette
26) Message boards : Questions and problems : Multiple WU progress toward completion (Message 32804)
Posted 14 May 2010 by Ross
Post:
Um, you read the thread on releasing .43/.44 but missed the reason why they were pulled? Even though I edited it into the first post and put it into the thread in its own post?

I must do better. ;-)

Rom Walton wrote:
Earlier today we pulled the last round of stable clients and rolled back to the stable clients that were available in early December.

A bug was introduced in 6.10.25 where the core client would continuously download new work from projects where the total GPU ram was enough to run the GPU app but not enough was available at run-time to actually run the application without crashing. This bug was fixed in 6.10.46.

As a result of having to pull the previous stable build we are moving forward with the 6.10.50 build as a potential release candidate build. I have adjust the test grouping to enable all of them now.

We really need to get a new stable version of the Mac client out the door, CUDA support for the Mac is not in the current stable Mac client.

Please report your results, good or bad, as quickly as possible.

----- Rom


I did read that but failed to notice that 6.10.46 was later than .43 I'm running. I recognized that .50 was later but that was future so I browsed past it. I guess since I don't have an appropriate GPU, the bug doesn't apply to me.

I think I may have a clue as to the perceived misbehavior, but it would take a lot of effort to confirm it.

I read somewhere that BOINC schedules WU (within a project) in the order in which they were d/l, absent some pre-defined urgency in the Report deadline. I suppose it's possible that Rosetta WUs were d/l in an order other than deadline order. Still, that doesn't explain why two WU due on the 19th were accumulating time together (one due AM the other PM).

BTW, is Report deadline time UTC?
27) Message boards : Questions and problems : Multiple WU progress toward completion (Message 32778)
Posted 13 May 2010 by Ross
Post:
I just realized that there's a discrepancy between BOINC scheduling SETI and Rosetta. I have NEVER seen BOINC schedule multiple SETI WU or even schedule a SETI WU out of Report deadline order. Yet that's consistently the behavior I see for Rosetta. I don't think we can blame this on Rosetta, since it's BOINC (6.10.43) doing the scheduling, not minirosetta 211.

Where can I find out why the BOINC releases after 6.10.18 have been withdrawn? This would help me decide if I should back off to the earlier release. I've read the thread about the release of 6.10.43 and 44, but it doesn't seem to address the problems I have, rather more on Mac.
28) Message boards : Questions and problems : Multiple WU progress toward completion (Message 32764)
Posted 12 May 2010 by Ross
Post:
I have 1 Rosetta WU due 5/14, 92.990% complete, 1:50:07 estimated time to completion. It hasn't accumulated much time recently

I have 1 R WU due 5/16 10:32:57 PM Ready to start.
I have 1 R WU due 5/16 10:32:57 PM also, 65.157% complete, 9:16:27 estimated. (Now running)
I have 1 R WU due 5/19 7:45:32 AM, 7.395% complete, 25:18:33 estimated.
I have 1 R WU due 5/19 10:42:38 PM, 72.406% complete, 7:17:04 estimated.
I have 1 new R WU due 5/21 Ready to start.

I have 1 SETI WU due 6/26, 88.719% complete, 00:35:39 estimated. (Only SETI, 50% share)

I'm seriously considering suspending the 5/21 WU so that it does not start for a while.

I have never seen a Waiting for memory message here, although I only have 2.5 Gig.
29) Message boards : Questions and problems : Multiple WU progress toward completion (Message 32708)
Posted 10 May 2010 by Ross
Post:
I let BOINC do its thing and I eventually got 5 WU for Rosetta. (I only have 1 for SETI but that's because the project keeps saying there are none available.)

The five WU are due 5/14, 5/16, 5/16, 5/19, & 5/19. All Rosetta work had accumulated on the 5/14 WU until I looked today, when the later 5/19 is now Running high priority. Checking the messages there were no mentions of memory, insufficient or otherwise.

Checking the Task Manager (Win XP) I see that the running WU (5/19 34%) has 122,144 K RAM, while the Waiting to run WU (5/14 73%) has 3,096 K RAM. While I will continue to observe these tasks, I'll keep my grubby fingers off of them, so BOINC can do its thing. My concern is that BOINC will preferentially schedule the WU due later and starve the WU due earlier, to the point where it may miss its deadline. BTW, Rosetta WU tend to to take 25 to 30 hours elapsed time. While running, the task tends to take 96 to 99% of the CPU, as my poor little fingers typing this note don't make much of a drain on it.
30) Message boards : Questions and problems : Multiple WU progress toward completion (Message 32562)
Posted 4 May 2010 by Ross
Post:
Sangletooth,

I'll go back to Rosetta to post, as more of the questions are there.

Ross
31) Message boards : Questions and problems : Multiple WU progress toward completion (Message 32545)
Posted 3 May 2010 by Ross
Post:
I just noticed that 6.10.18 is the recommended client. Should I back off from my current (optimized) 6.10.43?
32) Message boards : Questions and problems : Multiple WU progress toward completion (Message 32544)
Posted 3 May 2010 by Ross
Post:
On one of the projects I am running, multiple Work Units progress, in turn, toward completion (Rosetta). I have one CPU and have only claimed one CPU in my profile (at SETI under parl). I have asked for 4 days work in advance, mostly to outlast the weekly outages at SETI.

Recently, for example, I had 4 (Rosetta) WU and 3 of them were progressing toward completion. Two had a near report deadline (urgent). The third had a distant deadline but was still taking up processor time. My work around was to suspend it until the 2 urgent WU completed, but I'd rather not have to baby-sit my BOINC projects.

I am using (optimized) BOINC 6.10.43 on an older Windows XP computer. SETI is behaving as I would expect, with all fresh WU remaining in queue until each previous WU is completed. I am asking here because I believe that scheduling of WU is a BOINC issue, not a Rosetta issue.
33) Message boards : Questions and problems : BOINC 6.10.43 (Message 32431)
Posted 28 Apr 2010 by Ross
Post:
I am using (optimized) BOINC 6.10.43 on a Windows XP computer. I am running two projects, SETI and Rosetta. The SETI is currently working just fine and is getting enough WU ahead to go well past the Tuesday shut down (although it may not have happened this week - dunno). The Rosetta has a problem, which suspect is BOINC related, not Rosetta.

I have asked for 4 days WU in advance and seem to be getting it. But with Rosetta, if I have (for example) 4 WU 2 or 3 WU will progress toward completion, in turn. I have only one processor and only claim one processor in my profile (parl at SETI, not Ross Parlette at Rosetta). This became a problem recently when two WU were due soon and a WU which was not due for days and days was receiving processing time. I suspended it until the two urgent WU were complete, u/l, and reported. I don't really want to have to baby-sit my BOINC projects.

SETI is progressing fine, in that each WU is started, computed (sharing w/ Rosetta), and completed. As soon as it is completed, the processor switches to Rosetta or to a fresh SETI task. This is the behavior I have seen in the past and the behavior I expect to see. I'm not sure why I'm not seeing it with Rosetta. The point of d/l multiple WU is to have a back-log but not to process them all at the same time.

I have asked this question in the Rosetta and SETI fora, but they don't seem to be able to help me, since scheduling WU is really up to BOINC.

Thanks,

Ross

ps: where do I log in on the home page?
r


Previous 20

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.