Hi Grant,

A definite, maybe...
See how things go over the next day or so as they (hopefully) settle down.

Ok, will do. I'll only use my "trigger finger" if'n I see a great many ready to report when I'm gonna log into Winders.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

I have my cache settings at 'whatever you want' days plus an additional 0.05 days. That way, 'report after an hour' pretty much matches up with 'request work after an hour' and things potter along very harmoniously.

Hi Grant,
I have my settings at "Store at least [ 1 ] days of work" and "Store up to an additional [ 0.5 ] days of work". Do I need to change either of those 2 settings? I believe I have the old Linux PC set that way too.
Have a great day! :)
Siran

. . If you want your machine to report results more frequently try setting the 'additional work' value to zero. I have mine set like that on all 5 machines and as long as my caches are at nominal levels it reports every 5 mins.

Stephen

. .

In my case, I have to report frequently, more than 70 tasks reported at a time after outages results in Scheduler issues and nothing gets reported.

False logic. Even if you manage to report everything outstanding right at the beginning of an outage, you still have every task completed during the outage still waiting at the end. There are other ways of ensuring that the 'end of outage report' isn't too large, and they work even if we have a 12 hour outage or a 2 day outage next time.

Hi Grant,
Ok, will do. I'll only use my "trigger finger" if'n I see a great many ready to report when I'm gonna log into Winders.
Have a great day! :)
Siran

. . Or maybe only use it if the machine has not reported results in over 1 hour.

Stephen

:)

Once I used the parameter in the cc_config.xml file to reduce the # of reported tasks to something lower than 400-500 the server stopped having a hiccup every time I tried to report after the last Tuesday outage.

Some like this:

<cc_config>
 <log_flags>
   <sched_op_debug>1</sched_op_debug>
 </log_flags>
 <options>
   <use_all_gpus>1</use_all_gpus>
   <save_stats_days>90</save_stats_days>
   <max_file_xfers>16</max_file_xfers>
   <max_file_xfers_per_project>8</max_file_xfers_per_project>
 <max_tasks_reported>150</max_tasks_reported>
 </options>
</cc_config>

Tom

---

A proud member of the OFA (Old Farts Association).

If I remember correctly, Richard can confirm . . . . the client is hard-wired in the scheduler module to contact the project at minimum every hour. Yep, in cs_scheduler.cpp

// report results within this time after completion
//
#define MAX_REPORT_DELAY    3600

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Yes to both of those -

MAX_REPORT_DELAY 3600
<max_tasks_reported>150</max_tasks_reported>

- though I'd personally take <max_tasks_reported> even lower, to perhaps 64.

Only caveat: neither of those were included in the earlier versions of BOINC. If you're still using one of those, I'd seriously suggest you consider upgrading it: there are some good things in the newer versions, even if you have to do a little re-learning.

False logic. Even if you manage to report everything outstanding right at the beginning of an outage, you still have every task completed during the outage still waiting at the end.

<max_tasks_reported>150</max_tasks_reported>

Which is why I have that set to 75 to avoid Scheduler problems when reporting.
Avoid letting it build up to problem levels (when possible), and limit the number to avoid problems when it's not possible to avoid the build up in the first place.



Edit- oh, and it's taken a while but finally my Linux system is able to get work on most requests.

---

Grant
Darwin NT

Yes to both of those -
MAX_REPORT_DELAY 3600
<max_tasks_reported>150</max_tasks_reported>
- though I'd personally take <max_tasks_reported> even lower, to perhaps 64.

Only caveat: neither of those were included in the earlier versions of BOINC. If you're still using one of those, I'd seriously suggest you consider upgrading it: there are some good things in the newer versions, even if you have to do a little re-learning.

. . It's OK Wiggo, it is ONLY a recommendation, you can keep using your prehistoric version of BOINC :)

Stephen

:)

. . It's OK Wiggo, it is ONLY a recommendation, you can keep using your prehistoric version of BOINC :)

Stephen

But I'm not using Windows any more Stephen. ;-)

Cheers.

. . It's OK Wiggo, it is ONLY a recommendation, you can keep using your prehistoric version of BOINC :)

Stephen

But I'm not using Windows any more Stephen. ;-)

Cheers.

And he's using BOINC v7.14.2 :-) Well done, that man.

. . It's OK Wiggo, it is ONLY a recommendation, you can keep using your prehistoric version of BOINC :)

Stephen

But I'm not using Windows any more Stephen. ;-)

Cheers.

. . D'oh!

< Stephen slaps himself with a wet trout ... >

. . Damn, a perfectly good joke ruined/wasted ...

Stephen

:)

. . It's OK Wiggo, it is ONLY a recommendation, you can keep using your prehistoric version of BOINC :)

Stephen

But I'm not using Windows any more Stephen. ;-)

Cheers.

. . D'oh!

< Stephen slaps himself with a wet trout ... >

. . Damn, a perfectly good joke ruined/wasted ...

Stephen

:)

. . Damn, a perfectly good joke ruined/wasted ...
nope It just got backfired and got much funnier ...

I'll put that in once I remember how I setup munin :D

Excellent!

Ok I'll added both graphs. But I don't have historical data since I just added them

Ok I'll added both graphs. But I don't have historical data since I just added them

Thanks for that.
The graphs make it so much easier to see how things are going than having just the current numbers.

---

Grant
Darwin NT

Ok I'll added both graphs. But I don't have historical data since I just added them

Thanks for that.
The graphs make it so much easier to see how things are going than having just the current numbers.

Also I am sorry for anyone wanting those graphs to load the other million on the page... Just a side effect of graphing most projects

I'll put that in once I remember how I setup munin :D

Excellent!

Ok I'll added both graphs. But I don't have historical data since I just added them

Thank you very much!

On my wishlist: Result turnaround time (last hour average)
Its an good indication on when there are much shorties in the system.
Earlier this year (Aug) if the value went under 30h - then I suspected that the system will be in trouble in a couple of hours
I have not yet seen when start to be trouble again- 26h seems to be fine

Thanks again!

I'm starting to see a small amount in the Ready to Send Queue... 40K. I take this as a good sign. Are some of the faster machines now getting some WUs to fill the cache??

But I'm not using Windows any more Stephen. ;-)
Cheers.

. . D'oh!
< Stephen slaps himself with a wet trout ... >
. . Damn, a perfectly good joke ruined/wasted ...
Stephen
:)

. . Damn, a perfectly good joke ruined/wasted ...
nope It just got backfired and got much funnier ...

. . Glad it wasn't wasted ...

Stephen

:)