Posts by Mike Gibson

Info	Message
1) Message boards : Questions and problems : priority of tasks Message 100288 Posted 12 Aug 2020 by Mike Gibson	Sorry, I was referring to WCG where the deadline is 7 days regardless of how long the units take. Then any re-sends after 3.5 days get 3.5 days regardless. Mike
2) Message boards : Questions and problems : priority of tasks Message 100279 Posted 11 Aug 2020 by Mike Gibson	If we move on a stage. If you have units that are not completed within 3.5 days, your machine will not be considered as 'reliable' and so will not get re-sends which have only a 3.5 day deadline. If that is the case, then reduce the number of that project that you hold in cache in your Device Profiles. Mike
3) Message boards : Questions and problems : Projects Detach Message 36420 Posted 12 Jan 2011 by Mike Gibson	I am using BOINC Manager and found it under Tools rather than Advanced. Thanks, folks, I am crunching all 7 projects again. Mike
4) Message boards : Questions and problems : Projects Detach Message 36402 Posted 12 Jan 2011 by Mike Gibson	I was instructed to detach and reattach Cosmology. I detached but can't find out how to re-attach. Can anyone help, please. Mike
5) Message boards : Questions and problems : Task List Message 28757 Posted 14 Nov 2009 by Mike Gibson	Thanks, Gundolf, I have never had to do that before. Mike
6) Message boards : Questions and problems : Task List Message 28752 Posted 14 Nov 2009 by Mike Gibson	I notice that since 6.10.x, the task list only shows tasks which are under way. It doesn't show those which are ready to start or which are ready to report. Is this intended? I like to be able to manage my cache but without them being listed, it is impossible. Mike
7) Message boards : Questions and problems : Failure to get new work Message 27202 Posted 9 Sep 2009 by Mike Gibson	Many thanks, Jord. I now have a full set of WUs (apart from LHC, that is). Mike
8) Message boards : Questions and problems : Failure to get new work Message 27197 Posted 9 Sep 2009 by Mike Gibson	Hi, folks I have recently had a 5 week outage due to machine breakdown and installed 6.6.36 on its return. Since then I have been getting the following messages on WCG, Einstein & Rosetta: 09/09/2009 09:33:39 World Community Grid Message from server: No work sent 09/09/2009 09:33:39 World Community Grid Message from server: (won't finish in time) Computer on 79.6% of time, BOINC on 100.0% of that I was not surprised when I first restarted and the message was showing Computer on less than 10%, but now it is up to 80% it is a bit ridiculous. I have had to suspend a CPDN unit in order to get other projects. I have a dual core machine which effectively means that I have 48 hours a day available but if I divide the Time to Completion by the number of days remaining for each work unit and add, it only comes to 6 hours 37 minutes per day needed. So why does it think that any new WU's will not finish in time? Allowing for the 80%, I still have 30 hours a day available and Einstein and WCG units would take about 12 hours and Rosetta 1 day. I have the following weightings CPDN 280, Einstein 40, LHC 80, Rosetta 60, Seti 80 & WCG 100. Allowing for LHC being out of work for some time now and Seti replying no jobs available plus the 80%, that gives the following times available per day: CPDN 22.4 hours, Einstein 3.2 hours, Rosetta 4.8 hours & WCG 8 hours. They would all complete within the time available. This was never a problem before my machine broke down. Has anyone any ideas, please? Mike
9) Message boards : Questions and problems : BOINC 6.6.20 released for Windows, Windows x64, Linux, Linux x64 and MacOS X Message 24739 Posted 5 May 2009 by Mike Gibson	I have just installed 6.6.20 and have had the following problems. 1) BoincDV now comes up with tatally different figures for LTD from what was produced 2 days ago. Then I had a mixture of pluses and minuses adding up to zero. Now I have all negative except for LHC which is zero when it was +240,000. 2) My list of WUs for Seti doesn't match the list they have for me. Some are the same but others are different and recently returned WUs do not appear. Any ideas, please? Mike
10) Message boards : Questions and problems : 3 Projects running on Dual-core Message 21413 Posted 20 Nov 2008 by Mike Gibson	CPDN, WCG and either Seti or Rosetta. It happened twice yesterday, each time stopping when one of the 'running' units finished its 1 hour slot. I also run Einstein & LHC, but they were not involved.
11) Message boards : Questions and problems : 3 Projects running on Dual-core Message 21402 Posted 20 Nov 2008 by Mike Gibson	For some reason, I have 2 projects/WUs listed as 'running' but CPU time/progress is rising on 3. I have never seen this happen before. I am running 6.2.19 with Vista Premium on a Dual-core 3800+. Any comments, please?
12) Message boards : Questions and problems : BOINC Development Questions Message 20986 Posted 26 Oct 2008 by Mike Gibson	Thanks,Kathryn I had just closed down Boinc Manager when BoincDv told me to. Everything worked perfectly when I closed Boinc down, then made breakfast and then ran BoincDv. I still reckon Boinc Manager should allow 1 WU per project even when the debts are high. Cheers
13) Message boards : Questions and problems : BOINC Development Questions Message 20980 Posted 26 Oct 2008 by Mike Gibson	Jord Thanks. It seems that the current files were hidden . I must have found an early version which was not hidden. However, when I clear all debts on the current files and restart Boinc Manager, I still can't get Einstein & Rosetta WUs and then when I check BoincDv I find that all the debts have been restored. What can I be doing wrong, please? Mike
14) Message boards : Questions and problems : BOINC Development Questions Message 20977 Posted 26 Oct 2008 by Mike Gibson	Dagorath I tried BoincDv but found that the client_state files hadn't been updated since last November when I was only crunching 3 projects (CPDN, Seti & WCG). As it did not include LHC, I thought I had better not proceed with that. I then went onto the Projects page of Boinc Manager and Reset Project on LHC as I had no WUs on it. This resulted in several WUs downloading from WCG only. Still nothing on Einstein & Rosetta or Seti (but I wasn't worried about Seti as I still had an Astropulse WU). Doing Reset Project on Einstein & Rosetta still didn't result in any downloads. Help!
15) Message boards : Questions and problems : BOINC Development Questions Message 20975 Posted 25 Oct 2008 by Mike Gibson	Thanks, Dagorath I would have thought that BOINC Manager should be able to request a single WU per project where LTD is excessive and that project has no work. That way we would be able to continue crunching something until the owed project produced work. at which point BOINC Manager would then be able to restrict the others until either the LTD was cleared or the project ran out of work again. It should be a simple matter to enable just 1 WU to be downloaded when a project has run out of work. An automatic request for, say, 5 seconds of work should do the trick. The other amendment that is needed is for the Project page to show LTD data so that we can see if there is a problem building up. Cheers
16) Message boards : Questions and problems : BOINC Development Questions Message 20973 Posted 25 Oct 2008 by Mike Gibson	Hi I am running CPDN/Einstein/LHC/Rosetta/Seti/WCG using 6.2.19 with resource shares of 280/40/80/60/80/100 repectively on a dual-core machine. I have 2 CPDN WUs left, both with over 2000 hours remaining and one of which I have suspended, requiring only 12% & 13% of the allotted CPDN tme. Also 1 Seti Astropulse showing 53 hours remaining but I expect that to take about 90 instead needing 44% of Seti allotted time and 1 WCG(HPF) with only 13 mins left needing 0.2% of WCG allotted time. My cache is set for 10 days but I can't get any more units. LHC is out of work and Boinc is vainly trying to get 99,000 secs of work for that, I have set CPDN not to get any more WUs, but the other 4 projects seem to be a problem. I have tried doing a manual update on all 4 but the message each time says 'Requesting 0 seconds of work'. Why won't BOINC Manager let me ask for work, please? Is it a bug?
17) Message boards : BOINC client : Dual core Message 15704 Posted 7 Mar 2008 by Mike Gibson	Came across this thread while pondering a work-fetch problem. I think it's a related issue. Bear with me, this is going to get complicated. I have 8 cores. Neglecting projects which currently have no work or are disabled, they have been allocated: Share___Project__________STD____________LTD 200 ... CPDN ........ -6,253 ... -1,129,611 100 ... Einstein ... -21,185 ....... 74,984 300 ... SETI ....... -14,491 ....... 52,856 200 ... SETI Beta ... 41,931 ...... 495,423 Those shares add up to 800, so the cores should be working 2, 1, 3, 2 on the four projects. By the debt figures, SETI Beta should be the next to both fetch work and schedule a task. Yet I have only one SETI Beta task on board, and BOINC shows no sign of fetching another one. The single SETI Beta task I have is an Astropulse WU, currently estimating 202 hours remaining for a 19 March deadline. Tight, but with a 0.9888 efficiency for the machine as a whole, and a low CI/cache, there's no deadline pressure. In fact, it will finish in plenty of time, but BOINC doesn't know that (SETI Beta RDCFs are confused by having two separate applications under test). From previous experience - this has been nagging me for some time - BOINC will only start to fetch Beta work for a second core when the time remaining on the AP task has dropped below my cache setting (1 day). By then, STD will have bumped up against the limit stop of 86,400, and LTD will be up around 850,000 - both figures have gone up by over 1,000 since I started typing this. As Mike Gibson says, BOINC doesn't seem to be correctly allowing for the availability of extra cores when making work fetch calculations/decisions. My BOINC - as Ageless well knows - is my old faithful v5.10.13 for Windows: but I've checked the change log, and there's no report of any adjustment to this part of the scheduler since then. Edit - I've turned on <work_fetch_debug> in cc_config.xml - let's see what that throws up. At the moment, it's saying: 06/03/2008 13:52:03\|\|[work_fetch_debug] compute_work_requests(): cpu_shortfall 0.000000, overall urgency OK 06/03/2008 13:52:03\|SETI@home Beta Test\|[work_fetch_debug] project has no shortfall; skipping Richard I have just realised that BOINC is allowing for your projects that are out of work in case work becomes available by the next fetch, so your total is more than 800. However, the debt aspect should kick in, but unlikely to be continuous until the debt is cleared. The incorrect allowance for multicores in the fetch calculations could be why the debt is not being recovered. Try suspending other projects one at a time and doing an update on the project with the debt until BOINC asks for the right WU. Then reinstate the projects that you suspended. You may find that High Priority labels are assigned to some WUs again because of the incorrect allowance for multicores. However these are likely to be short-lived and you should find that the debt eases gradually. The High Priority labels could return for reducing periods for a while. Mike
18) Message boards : BOINC client : Dual core Message 15703 Posted 7 Mar 2008 by Mike Gibson	I don't think BOINC ever designates a specific core for a particular project or task. Mo That was what we were saying, but also that it is possible to manually force it to happen. However, the main issue was that BOINC is not allowing for multi cores correctly in assessing WU fetches. Mike
19) Message boards : BOINC client : Dual core Message 15701 Posted 6 Mar 2008 by Mike Gibson	Came across this thread while pondering a work-fetch problem. I think it's a related issue. Bear with me, this is going to get complicated. I have 8 cores. Neglecting projects which currently have no work or are disabled, they have been allocated: Share___Project__________STD____________LTD 200 ... CPDN ........ -6,253 ... -1,129,611 100 ... Einstein ... -21,185 ....... 74,984 300 ... SETI ....... -14,491 ....... 52,856 200 ... SETI Beta ... 41,931 ...... 495,423 Those shares add up to 800, so the cores should be working 2, 1, 3, 2 on the four projects. By the debt figures, SETI Beta should be the next to both fetch work and schedule a task. Yet I have only one SETI Beta task on board, and BOINC shows no sign of fetching another one. The single SETI Beta task I have is an Astropulse WU, currently estimating 202 hours remaining for a 19 March deadline. Tight, but with a 0.9888 efficiency for the machine as a whole, and a low CI/cache, there's no deadline pressure. In fact, it will finish in plenty of time, but BOINC doesn't know that (SETI Beta RDCFs are confused by having two separate applications under test). From previous experience - this has been nagging me for some time - BOINC will only start to fetch Beta work for a second core when the time remaining on the AP task has dropped below my cache setting (1 day). By then, STD will have bumped up against the limit stop of 86,400, and LTD will be up around 850,000 - both figures have gone up by over 1,000 since I started typing this. As Mike Gibson says, BOINC doesn't seem to be correctly allowing for the availability of extra cores when making work fetch calculations/decisions. My BOINC - as Ageless well knows - is my old faithful v5.10.13 for Windows: but I've checked the change log, and there's no report of any adjustment to this part of the scheduler since then. Edit - I've turned on <work_fetch_debug> in cc_config.xml - let's see what that throws up. At the moment, it's saying: 06/03/2008 13:52:03\|\|[work_fetch_debug] compute_work_requests(): cpu_shortfall 0.000000, overall urgency OK 06/03/2008 13:52:03\|SETI@home Beta Test\|[work_fetch_debug] project has no shortfall; skipping Richard I have a 50% allocation to CPDN and with 2 cores, it seemed odd that BOINC wouldn't let CPDN have 1 core and divide up the other core between my other projects. Instead CPDN had 2 WUs part of the time and none at others. I thought this must be wasting computing time with all the stopping and starting, so at one point I was forcing it by setting CPDN to not get more tasks and by suspending the second task. This seemed to work well and could probably work for 8 cores but it would require a lot of monitoring. However, I had to abandon that approach when I started doing LHC which only has work available part-time. Sometimes the WUs are finished in seconds, but BOINC has supplied as many as 40 WUs over a period to keep my machine crunching as long as possible. Cheers Mike
20) Message boards : BOINC client : Dual core Message 15700 Posted 6 Mar 2008 by Mike Gibson	The RDCF is 1.195342. Hasn't that already been incorporated in the Time to Completion? That's quite a healthy number. It has been incorporated into the time to completion, but it changes during and after each individual task. So if you have one task that runs for an hour, while the estimate was 2 hours, the RDCF goes down. If then the next task takes 3 hours, where the ETC is again 2 hours, it goes back up. The biggest question is, on which project do you see this? (Or projects, if more). I am mostly getting it on LHC. I wouldn't worry about any others because they have all utilised LHC time and catch up eventually. LHC only has work for brief periods so it is particularly galling to be refused work unnecessarily when there is a hefty debt. LHC, of course, never catches up. By the way, where can I find the official debt figures? I have done my own figures to check. Regards Mike Mike

Copyright © 2026 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.