Posts by ChertseyAl
log in
1) Message boards : Number crunching : Limit on number of WUs perhaps a little low? (Message 602)
Posted 2245 days ago by Profile ChertseyAl
Unfortunately I'm still only getting 20 WUs per host:

25/05/2012 09:45:01|CAS@home|Sending scheduler request: To fetch work. Requesting 106231 seconds of work, reporting 0 completed tasks
25/05/2012 09:45:06|CAS@home|Scheduler request succeeded: got 0 new tasks
25/05/2012 09:45:06|CAS@home|Message from server: No tasks sent
25/05/2012 09:45:06|CAS@home|Message from server: This computer has reached a limit on tasks in progress

Don't worry about it, it's not that important. I have some Tsinghua Nano Tech Research WUs now which look like they will take a bit longer to run :)


2) Message boards : Number crunching : Limit on number of WUs perhaps a little low? (Message 598)
Posted 2246 days ago by Profile ChertseyAl
I don't micromange my hosts, so generally like to have a cache of around 24 hours work, but could get by with 12 hours. Sadly, the most work I can cache is around 9 hours with this project :(

I wonder if the limit of WUs could be raised a bit?


3) Message boards : Number crunching : Low credit (Message 339)
Posted 2657 days ago by Profile ChertseyAl
Sorry,but 0.01 or 0.02 credit for over 20min runtime that's a joke i hope.

Yes, I came back to this project only to find a daily RAC of 38! Even my slow hosts should make 200-300.

Obviously something wrong, NNW for a while. Again.

4) Message boards : Number crunching : cas is suspended until problem is fixed (Message 174)
Posted 2887 days ago by Profile ChertseyAl
I've been following this issue for some time, as I too have stopped crunching it because of the aborts. I crunch, and have crunched, many projects. This is one of the worst in terms of 'ease of use' for the volunteer. And it's volunteers that you rely upon.

The answer is that the project server has to wait before the WU exceeds the deadline( BOINC default value is 7 days), and then sends another copy of WU to another computer. It is not acceptable to scientists who want results quickly.

Ok ...

1) Wasting volunteers computer time, electricy costs etc is unacceptable. Full stop. Just credit the redundant result if you insist on setting IR higher than MQ. Even LHC saw the error of their ways and abandoned this crazy scheme.

2) If you need the results sooner, set a tighter deadline. Try 5 days. or 3 days. Don't set it any lower as your project will force every client into panic mode and annoy volunteers.

3) Have you considered that maybe BOINC isn't a suitable platform for this project? There are many projects that don't use it. BOINC is meant to be easy and friendly for volunteers to use. Tight deadlines and frequent aborted WUs make it neither.

4) I'm not an expert on BOINC, but I do run 10 PCs dedicated to it (and a couple of others in more general use), and in the height of Summer burning a kilowatt of electricity for no reward is not something that makes me happy ;)

Don't take any of the above personally - It's sometimes tricky to get a project running smoothly and I hope you reach a sensible compromise between your requirements and those of the volunteers :)