Message boards :
Number crunching :
Resource share - can't get the balance right
Message board moderation
Author | Message |
---|---|
GlobalWarring Send message Joined: 8 Mar 09 Posts: 42 Credit: 11,041,680 RAC: 952 |
OK so the objective was to crunch only SETI units unless I had no work to process which as we know is a more frequent scenario than any of us would like.... So I configured the resource share as; SETI 300 / Orbit 1 / Einstein 1 figuring this would only allow Einstein to run where there was no SETI work available. What seems to be happening is that the work is being processed according to deadline and irrespective of the project. Having put my team Totally Inbound in the top 10 UK contributors to SETI by RAC I would like to keep us there so your help would be appreciated. Thanks in advance guys for your help. David |
juan BFP Send message Joined: 16 Mar 07 Posts: 9786 Credit: 572,710,851 RAC: 3,799 |
What you need to do is put the resource share of the backup project at 0 (zero) not 1 (one), by doing that your host will crunch that project only when out of work from SETI. |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
Use 0 for backup projects. Otherwise BOINC will run the projects normally in it's time% debt system. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
GlobalWarring Send message Joined: 8 Mar 09 Posts: 42 Credit: 11,041,680 RAC: 952 |
Thanks Guys, Doh! So simple when you know how :-) David |
MikeN Send message Joined: 24 Jan 11 Posts: 319 Credit: 64,719,409 RAC: 85 |
Just one problem, some projects (e.g. Cosmology) will not allow you to give it a resource share of 0. |
juan BFP Send message Joined: 16 Mar 07 Posts: 9786 Credit: 572,710,851 RAC: 3,799 |
Not sure if works with Cosmology but you could tray to edit the project configuration file manualy, look in the E@H file (I don´t run cosmology so not know what is their file name but must be something similar): account_einstein.phys.uwm.edu.xml or account_setiathome.berkeley.edu.xml for example edit and change the resource_share from 100 to the zero. <project_preferences> <resource_share>0</resource_share> Don´t forget to restart the entire Boinc after that (not just the Boincmgr) and if you click the read configuration file buttom the settings will be override with the old values (100 or whatever you use). Maybe when Richard awake he could give you another better way to do that. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
Not sure if works with Cosmology but you could tray to edit the project configuration file manualy, look in the E@H file (I don´t run cosmology so not know what is their file name but must be something similar): Zzzzzzz :P Remember to change it for whichever venue is active, too: <venue name="home"> <resource_share>100</resource_share> But I lifted that out of a sched_reply file, so the likelihood is that it would get reset to whatever the project website accepts the first time it's used. Of course, we would hope that you don't need to call on a backup project for months at a time... |
David S Send message Joined: 4 Oct 99 Posts: 18352 Credit: 27,761,924 RAC: 12 |
OK so the objective was to crunch only SETI units unless I had no work to process which as we know is a more frequent scenario than any of us would like.... You do understand that once your machine has downloaded work for a backup project, it will go ahead and process that work even if it subsequently gets new work for your main project. David Sitting on my butt while others boldly go, Waiting for a message from a small furry creature from Alpha Centauri. |
GALAXY-VOYAGER Send message Joined: 21 Oct 12 Posts: 85 Credit: 157,743 RAC: 0 |
One thing that nobody has apparently mentioned. orbit@home Is Not Active, and Has not been Active for a number of months. besides seti@home (which is what i first became involved with, because of my Interest in The Project, and which is my Favorite Project), I have found that einstein@home and rosetta@home seem to give me more work tha the others that i am involved with: However, this may just be coincidence. GALAXY-VOYAGER |
skildude Send message Joined: 4 Oct 00 Posts: 9541 Credit: 50,759,529 RAC: 60 |
orbits hasnt been active in more than a couple of months. They havent had work for several years now. Interestingly, another project Asteroids@home is doing almost the exact same search as Orbits was In a rich man's house there is no place to spit but his face. Diogenes Of Sinope |
William Send message Joined: 14 Feb 13 Posts: 2037 Credit: 17,689,662 RAC: 0 |
One thing that nobody has apparently mentioned. Orbit is currently considered a dead project and has been taken off the official list of active projects. It doesn't matter if people are still attached to it, as BOINC will only periodically poll the scheduler server and, if there are no replies, the master url - it keeps trying at such a low level, that you won't notice a thing. I just checked with Rosetta and it still is one of the projects running such an old server version that it does not accept a resource share of 0, so doesn't work so well as a pure backup project - for a BOINC 7 setting a low share will result in minimal work while SETI has tasks and in a good supply when it doesn't. Older Boinc versions will try to keep at least one task of such a project on the rig at all times, so more (unwanted) work will get done. Einstein almost always has work and will gladly fill up your cache if you let it. BOINC 7 workfetch algorithm means that it will try to keep the balance - when SETI workflow is stable, you'll see the host stablise in running equal shares (if you are set up for that). Older boinc versions again may not be so good at that. A person who won't read has no advantage over one who can't read. (Mark Twain) |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
One thing that nobody has apparently mentioned. I'd just say that BOINC v7 seems to take an awful long time to settle back down into equilibrium if a new project is introduced to the mix, whether by user choice or by way of a backup fetch. Allow about a week... BOINC v6 is better, but you're still probably counting in days. |
GALAXY-VOYAGER Send message Joined: 21 Oct 12 Posts: 85 Credit: 157,743 RAC: 0 |
yes, i still have it Attached, but i have Suspended it and about once every 2 or 3 weeks, I resume it for a day or two and see if anything has changed. GALAXY-VOYAGER |
Fred E. Send message Joined: 22 Jul 99 Posts: 768 Credit: 24,140,697 RAC: 0 |
I'd just say that BOINC v7 seems to take an awful long time to settle back down into equilibrium if a new project is introduced to the mix, whether by user choice or by way of a backup fetch. Allow about a week...I'm using the option <rec_half_life_days>1</rec_half_life_days> with v7 and it will settle after a day. The defau1t is 10 days. Client configuration I still have to use a low cache setting and no-new-tasks to keep things in balance when running more than one project. Another Fred Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop. |
rob smith Send message Joined: 7 Mar 03 Posts: 22202 Credit: 416,307,556 RAC: 380 |
By suspending and re-starting you are actually making it very difficult for BOINC to sort its life out. Either leave everything running, or drop the project. Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
David S Send message Joined: 4 Oct 99 Posts: 18352 Credit: 27,761,924 RAC: 12 |
One thing that nobody has apparently mentioned. Orbit has actually shut down its Boinc servers. Only the web site is still up and running. I'll take a look at asteroids. Einstein almost always has work and will gladly fill up your cache if you let it. That's for dang sure! BOINC 7 workfetch algorithm means that it will try to keep the balance - when SETI workflow is stable, you'll see the host stablise in running equal shares (if you are set up for that). Older boinc versions again may not be so good at that. Are 6.10.58 and 6.10.60 okay? David Sitting on my butt while others boldly go, Waiting for a message from a small furry creature from Alpha Centauri. |
Horacio Send message Joined: 14 Jan 00 Posts: 536 Credit: 75,967,266 RAC: 0 |
Im using 6.10.60 and it doesnt try really hard to keep the balance. At least not as hard as I wish... In that version the cache is always filled with the project that can supply work. As SETI is never able to give as much work as requested then it falls behind. In the loooooong run, as the "debts" go highly unbalanced it will try a bit harder but anyway, it's not ussually enough to put the shares were they should be... |
rob smith Send message Joined: 7 Mar 03 Posts: 22202 Credit: 416,307,556 RAC: 380 |
Two of my crunchers are running 6.10.x BOINC. They have taken a long time (months, not hours or days) to become stable, and remain so. You have to be careful in how you set the resource share for each project. I have found that by setting the main project to 1000, and the other projects to a significantly lower level, in the range 10-50 each I get the desired split. I also run a number of resource-zero projects. The averaging appears to take several time the longest deadline to reach stability, and S@H has about the longest deadline for "normal" tasks, at about a month, so you can expect to wait say three or four months before any sort of stability is reached. Oh, and don't be tempted to fiddle during that time, as fiddling always upsets things in an unpredictable manner.... Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
Two of my crunchers are running 6.10.x BOINC. They have taken a long time (months, not hours or days) to become stable, and remain so. A new feature starting with 7.0.40 is the use of a file app_config.xml to control the number of tasks can run for a given app/project. Which can keep BOINC from putting all of the host resources into one project. Like the machine where I run SETI@Home beta. I have it limited to running 1 task for beta. So when it does get work from beta it doesn't take over the whole machine for weeks. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.