OK, I can see that the machine with 4 projects did a bunch of EAH work ending at around the 15th July with no new work since then. The crunching of that EAH work was probably done at an accelerated rate so as to avoid missing deadlines and this would have left EAH with a negative LTD. As the other projects crunch and because you have now reduced your queue to 1 day, your work on hand will reduce and become more manageable and the EAH negative LTD will reduce and eventually become positive. At this point new EAH work will be downloaded and you will start cycling between projects according to your resource share. Hopefully this will only take a few more days and everything will be looking good and stable.
How much work do you have for the other three projects?
Right now only the climate at 12%, one seti at 15%, and 3 seti pending. I think that protein have the same EAH problem. Between 21/7 and 22/7 download, finished and upload a bunch of work, and now doesn`t download any. :(
Well, only can wait and adjust more "gently" the setups in the future.
OK, I can see that the machine with 4 projects did a bunch of EAH work ending at around the 15th July with no new work since then. The crunching of that EAH work was probably done at an accelerated rate so as to avoid missing deadlines and this would have left EAH with a negative LTD. As the other projects crunch and because you have now reduced your queue to 1 day, your work on hand will reduce and become more manageable and the EAH negative LTD will reduce and eventually become positive. At this point new EAH work will be downloaded and you will start cycling between projects according to your resource share. Hopefully this will only take a few more days and everything will be looking good and stable.
How much work do you have for the other three projects?
Right now only the climate at 12%, one seti at 15%, and 3 seti pending. I think that protein have the same EAH problem. Between 21/7 and 22/7 download, finished and upload a bunch of work, and now doesn`t download any. :(
Well, only can wait and adjust more "gently" the setups in the future.
Greets...
With my v4.45 clients I actually run with .7 day connect time and it works great for me. Mr Keck had a formula for the max setting ... I think it was something like this... shortest work return time in days divided by number of projects = time between connect setting. So if the shorted project were E@H with a 7 day (I think) return date and you had 4 project running 7/4 = a MAX connect time of 1.75. Using his formula again, I run a project with 4.5 day return times and 6 projects so 4.5/6 = .75 MAX days between connects. This formula has proven to establish a connect time that works very well on all my machines of widely varying speeds from PII 266Mhz to AMD 2.3GHz and from 3 to 7 projects. I would strongly recommend you try his Max connect time formula.
[shameless] If you want to see what your short and long term debts are on one screen, try BoincDV[/shameless]. Good luck, Skip
I would say no in this case. Since CPDN and E@H are about balanced, and PP@H and S@H are also close to balanced. This tends to indicate that the client is working as it should. PP@H & E@H have recently been hogging the CPU and it is time for CPDN & S@H to catch up.
RE: OK, I can see that the
)
Right now only the climate at 12%, one seti at 15%, and 3 seti pending. I think that protein have the same EAH problem. Between 21/7 and 22/7 download, finished and upload a bunch of work, and now doesn`t download any. :(
Well, only can wait and adjust more "gently" the setups in the future.
Greets...
RE: RE: OK, I can see
)
With my v4.45 clients I actually run with .7 day connect time and it works great for me. Mr Keck had a formula for the max setting ... I think it was something like this... shortest work return time in days divided by number of projects = time between connect setting. So if the shorted project were E@H with a 7 day (I think) return date and you had 4 project running 7/4 = a MAX connect time of 1.75. Using his formula again, I run a project with 4.5 day return times and 6 projects so 4.5/6 = .75 MAX days between connects. This formula has proven to establish a connect time that works very well on all my machines of widely varying speeds from PII 266Mhz to AMD 2.3GHz and from 3 to 7 projects. I would strongly recommend you try his Max connect time formula.
[shameless] If you want to see what your short and long term debts are on one screen, try BoincDV[/shameless]. Good luck, Skip
Ok, that´s my debt numbers in
)
Ok, that´s my debt numbers in this machine, courtesy of BoincDV
It's clearing a good option?
RE: Ok, that´s my debt
)
I would say no in this case. Since CPDN and E@H are about balanced, and PP@H and S@H are also close to balanced. This tends to indicate that the client is working as it should. PP@H & E@H have recently been hogging the CPU and it is time for CPDN & S@H to catch up.
BOINC WIKI
BOINCing since 2002/12/8