Posts by theCase

1) Message boards : Number crunching : Time estimates seem less than optimal (Message 97471)
Posted 19 Jun 2020 by theCase
Post:
While I understand the thought process of "how can one plan for three day shutdown" , consider this:

    My target CPU time is 2 hours,
    Time devoted to Rosetta is 15% (as opposed to other projects).
    MY CPU is on 25% of the time.


These three items are available to the scheduler.

Why do I get ten work units with an estimated run time of 10 hours all at once? Why are they due in three days?

In a perfect world, the scheduler would send me one task every few days, (e.g 15% of 6 hours a day is 54 minutes of CPU time dedicated to Rosetta), instead the scheduler sends nothing for days, then slams my PC with 100 hours worth of tasks due in three days.

I feel there may be a problem with the scheduler...

2) Message boards : Number crunching : Time estimates seem less than optimal (Message 97462)
Posted 19 Jun 2020 by theCase
Post:
Why does Rosetta send me 8 hour work units when I specify 2 Hour WU's?Have you saved those changes? Yes, as of two/three months ago.
If they aren't saved, then then changes won't be sent through the next time the computer contacts the project.

Why does Rosetta send me WU''s due in three days when they can't be finished?What makes you think they can't be finished? my PC "duty time" is about 25% and I'll be turning off my PC for the next several days, it will probably be off till the 22nd. (the 10 Rosetta tasks currently running are due on 6/21)
As i pointed out, 16 hours is all that's needed to finish them.


If you're so concerned about what is being sent, turn on the CPU scheduling debug option for the Event log & see what is being asked for and why (BOINC Manager, Advanced view, Options, Event log options).[/quote] Weird, I never noticed the "event log options" even after running BOINC for 20 years, I will take a look! Thanks for all your help.[/size]
3) Message boards : Number crunching : Time estimates seem less than optimal (Message 97454)
Posted 19 Jun 2020 by theCase
Post:
I will change my settings as you recommend:

    But why do other projects (WCG) NOT have a problem with my settings?

    Why does Rosetta send me 8 hour work units when I specify 2 Hour WU's?

    Why does Rosetta send me WU''s due in three days when they can't be finished?


As I mentioned, I believe there are problems in the scheduler algorithm. Something is not right....

4) Message boards : Number crunching : Time estimates seem less than optimal (Message 97444)
Posted 18 Jun 2020 by theCase
Post:
I also have a problem with Rosetta having short deadlines. Rosetta consistently sends work units that cannot be finished in time. Currently I have ten(!) work units estimated at 8 hours each.

I've set up my "target CPU time" to two hours, "store at least" is 0.1, "additional" is 0.5, My PC is on 25% of the time with BOINC available 99.9%. Resource share is set to 15% (WCC plays a lot nicer). This is on an Intel I7-77xx eight core laptop.

Given the information Rosetta has available why does it continue to send WU's that will not be finished? I'd like to look at the scheduler code you're using because it is not doing a good job.
5) Message boards : Number crunching : No new work (Message 64667)
Posted 31 Dec 2009 by theCase
Post:
All the computing power that has been donated freely, going unused. I guess I'm missing the reason behind the apparent lack of urgency to fix whatever is broken.


It's not going to "waste" if you run multiple projects.

If you're not on multiple projects you're just a credit-obsessive, fanboy that cares only for points and not the science.

Just my opinion.






©2020 University of Washington
https://www.bakerlab.org