| Author | Message |
|
|
|
I got MalariaControl's Resource share at normal (100), with switch between Project Clients set to 60 Minutes.
MalariaControl is running alongside 3 other Projects (CPDN, LHC [no work] and EAH), all of which are set at default Resource share (100) as well.
Since I got it running on all Systems, I've seen it progressively displace all other Projects on all machines.
Since attaching to MC, my entire Network has effectively ceased switching to other Project's Clients alltogether and is by now running MC at 100% capacity - which isn't so bad, but not desired in the long run *g* -
The way I understand BOINC (V5.2.13) switching mechanism, there shouldn't be any exception to Switching between Applications e.g. for new attached Projects (at least I never observed such a behaviour with any BOINC Version)
Note : all BOINC settings are default, except "Keep Applications in Memory" is enabled. I'm using mostly Linux and two Win32 machines.
Can anyone else confirm this ?
____________
Scientific Network : 44800 MHz - 77824 MB - 1970 GB
 |
|
|
|
|
|
Hi FalconFly,
I am having a similar problem.
I have malaria @ 30 share with 11 %.
On all three of my computers there has been no switching. I suspended all work (not projects, WU's individually) and then resumed one the suspended work units. After doing this, malaria began to switch projects.
On my primary machine i haven't done this, being as i have a ton of work to suspend and don't mind devoting all of my resources to malaria at the moment
I hope the operators and mods take a look at this and work the kinks out.
Happy crunching everyone!
Mike
Post Script: Maybe a reboot or restart of BOINC will fix this. I will give it a try and if switching starts after a reboot, i will update you.
[edit]
Post Script 2: Ok, i rebooted and it isn't switching at the moment, perhaps in an hour or so it will.
Could it possibly be that, while other projects have more %, MC has nearly 90% of the WU's on my work list? If 140 units need completion in a few days, could my scheduler just be allocating resources to where they are needed most; and not by resource %?
____________
"The most incomprehensible thing about the universe is that it is comprehensible"
-Albert Einstein

my homepage |
|
|
|
|
|
Have you checked out the figures for Long Term and Short Term Debt....
You can use BOINC Debt Viewer to find out the figures.
From the Boinc Wiki
Short Term Debt
Short term debt drives which project gets the CPU next if the CPU is in Highest Debt First mode. All projects with no work on the computer have a short term debt of 0. Short term debt is shifted for all projects so that the average debt for all projects that have active work on the Host is 0.
Long Term Debt
Long term debt is part of the decision of which project to download from next. If the long term debt is less than negative Queue Size no work request will be made of that project unless a CPU is idle. Long term debt is shifted such that the mean is always 0 (the sum of all Long Term Debt values is 0).
____________

www.chris-kent.co.uk aka Chief.com |
|
|
|
|
|
Clark, Thanks a ton.
I should have searched the wiki.
I have huge negative debt on both short and long term for MC.
I read this on the wiki:
"In Earliest Deadline First mode, the Work Scheduler runs Results with the nearest deadline. This allows the BOINC Client Software to meet deadlines that would otherwise be missed. Earliest Deadline First mode is entered if either a Work Unit has a Deadline that is very near, the Result is due in less than twice the "connect to" time, or the Work Scheduler determines that one of the Results will nearly not be completed on time."
That must be what's going on.
Thanks yet again,
Mike
Post Script: as mentioned in a previous thread, about the amount of WU's sent out, i would think MC would adjust how many they send; 140 (in my case) seems to be quite a bit. (or maybe i should connect more than every 1.8 days)
____________
"The most incomprehensible thing about the universe is that it is comprehensible"
-Albert Einstein

my homepage |
|
|
|
|
|
As I looked at it today, everything appears back to normal, so whatever the Problem was (new attached Projects shouldn't have a chance to have any debt right from the start IMHO)... It's gone for now :)
____________
Scientific Network : 44800 MHz - 77824 MB - 1970 GB
 |
|
|
|
|
|
I have another thread on the deadline. Because the wu's here came on mass and have a really short deadline, the machine goes into EDF, and crunches it's way out of it's perceived predicament.
As you have now seen, the LTD goes wildly negative, so they get their results quick, but then no more for ages.
____________
Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.
 |
|
|
maireForum moderator Project administrator Project scientist Send message Joined: Nov 7 05 Posts: 406 Credit: 58,577 RAC: 0
|
|
An explanation for the short deadlines: thread on deadlines
____________
Nicolas Maire
Swiss Tropical Institute |
|
|
|
|
|
hmm. Good thing I did what I always do with new projects: Suspend all others for a period of time to get some initial work done for the newly added project ;)
____________
 |
|
|
|
|
hmm. Good thing I did what I always do with new projects: Suspend all others for a period of time to get some initial work done for the newly added project ;)
The latest version (read: with all the MS updates) of XP seems to be causing problems with the proper running of the round robin function. Mind you, this is also on an Intel dual-core machine; all my AMD-based W2003 servers are running just fine.
____________
Rejoignez le Zongo sQuad, la preuve vivante que le rire est un puissant m�dicament. |
|
|