I've been sitting on version 6.6.36 for months now and was wondering if an upgrade to 6.10.x would be to my benefit? I'm not running CUDA and I'm using all optimized apps. What features might I be missing out on?

---

"Life is a tragedy for those who feel, and a comedy for those who think."

"I never get into an argument that I cannot win."

You'll probably hear other opinions, but if I wasn't doing GPU processing, I'd be using 5.10.45 (as I am on my one non-GPU machine).
I see no reason why you need to update.

-Dave

---

I've been sitting on version 6.6.36 for months now and was wondering if an upgrade to 6.10.x would be to my benefit? I'm not running CUDA and I'm using all optimized apps. What features might I be missing out on?

There is a libcurl.dll fix in one of the new versions. I don't recall if it was 6.10.18 or if it was 6.10.2x. Also in the tasks list there is an option to only display active tasks. I think 6.10.xx versions also have "don't pound the crap out of the servers" code in them.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the BP6/VP6 User Group today!

I've been sitting on version 6.6.36 for months now and was wondering if an upgrade to 6.10.x would be to my benefit? I'm not running CUDA and I'm using all optimized apps. What features might I be missing out on?

It's not a factor with SETI, but on some other projects it's helpful to know when the application is (or is not) doing checkpoints. 6.10.18 has a properties button that allows you to see when the last checkpoint occurred, amongst other information. Yeah, you can have checkpointing listed in the log if you want, but that's a LOT of log messages if you're checkpointing frequently.

Also, you can do multiple selections using shift-click or control-click. That's very handy for those "oops, I didn't really want to get those 500 WUs" types of situations.

I have been using 6.6.36 for awhile now and I see no point of upgrading even though I am getting messages to upgrade. So I will wait until we have to upgrade with a new optimised version comes out which will only work with the new versions of BOINC

---

I've been sitting on version 6.6.36 for months now and was wondering if an upgrade to 6.10.x would be to my benefit? I'm not running CUDA and I'm using all optimized apps. What features might I be missing out on?

There is a libcurl.dll fix in one of the new versions. I don't recall if it was 6.10.18 or if it was 6.10.2x. Also in the tasks list there is an option to only display active tasks. I think 6.10.xx versions also have "don't pound the crap out of the servers" code in them.

The libcurl fix does away with all the ugly mucking around with the "hosts" file when a project has more than one server listed in DNS but one of them is down.

... and the "don't pound the crap out of the servers" code will mean quicker recoveries once enough people get on board.

---

I've been sitting on version 6.6.36 for months now and was wondering if an upgrade to 6.10.x would be to my benefit? I'm not running CUDA and I'm using all optimized apps. What features might I be missing out on?

It's not a factor with SETI, but on some other projects it's helpful to know when the application is (or is not) doing checkpoints. 6.10.18 has a properties button that allows you to see when the last checkpoint occurred, amongst other information. Yeah, you can have checkpointing listed in the log if you want, but that's a LOT of log messages if you're checkpointing frequently.

Also, you can do multiple selections using shift-click or control-click. That's very handy for those "oops, I didn't really want to get those 500 WUs" types of situations.

I've been able to do that since I started crunching again in July with 6.6.something .28 maybe?

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the BP6/VP6 User Group today!

A new feature in 6.10.32 allows for a true back up project. Setting a project Resource Share at 0 will tell Boinc to only ask that project for work if a CPU become idle. It's still to be tested in the real world since older server software won't let you enter 0 for RS although .001 may be read by Boinc as 0.

A new feature in 6.10.32 allows for a true back up project. Setting a project Resource Share at 0 will tell Boinc to only ask that project for work if a CPU become idle. It's still to be tested in the real world since older server software won't let you enter 0 for RS although .001 may be read by Boinc as 0.

Since the resource share is a double, 0.0001 will be read as 0.0001 and not 0.

---

BOINC WIKI

A new feature in 6.10.32 allows for a true back up project. Setting a project Resource Share at 0 will tell Boinc to only ask that project for work if a CPU become idle. It's still to be tested in the real world since older server software won't let you enter 0 for RS although .001 may be read by Boinc as 0.

Since the resource share is a double, 0.0001 will be read as 0.0001 and not 0.

Your are correct larger values didn't work, although showing 0 in the projects page, but testing on Spinhenge, SZTAKI and LHC with a value of .0000001 gave me <resource_share>0.000000</resource_share> in the client_state.xml

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

A new feature in 6.10.32 allows for a true back up project. Setting a project Resource Share at 0 will tell Boinc to only ask that project for work if a CPU become idle. It's still to be tested in the real world since older server software won't let you enter 0 for RS although .001 may be read by Boinc as 0.

Since the resource share is a double, 0.0001 will be read as 0.0001 and not 0.

Even though its read as 0.0001 and not 0, the backup project function as it should. Like today for example, i ran out of seti wus, gpugrid as my backup project kicks in.

---

A new feature in 6.10.32 allows for a true back up project. Setting a project Resource Share at 0 will tell Boinc to only ask that project for work if a CPU become idle. It's still to be tested in the real world since older server software won't let you enter 0 for RS although .001 may be read by Boinc as 0.

Since the resource share is a double, 0.0001 will be read as 0.0001 and not 0.

Even though its read as 0.0001 and not 0, the backup project function as it should. Like today for example, i ran out of seti wus, gpugrid as my backup project kicks in.

True, as was argued on the mailing list as well as many forums, a large differential in RS acts as a work around, but it isn't as effective as a true back up project. You can still end up with more work than desired and that can delay getting work from your main project(s). If the new algorithm works properly, you should get only enough work to keep the CPU(s) warm and the BU project wont hog the system until all it's WUs have been processed.

Is there any one version which stands out for particularly good performance, in terms of work done for CPU/GPU time expended?

---

Is there any one version which stands out for particularly good performance, in terms of work done for CPU/GPU time expended?

There shouldn't be any difference in terms of work done between any version of BOINC with "reasonable" settings (or even fairly unreasonable ones).

Some of the older versions had trouble following resource shares if you're doing more than one project and had deadlines and/or carried a big cache. These versions put too much priority on keeping the cache full, and a project that always had work would get more than their allocated resource share.

Some work is being done to avoid starting a bunch of work units for a given project when there is deadline pressure -- this is mostly cosmetic. Mostly.

Later versions are easier on the servers -- some think that being slower to report is a huge issue, but it cuts down on retries and wasted resources at the server end.

... and the libcurl fix takes care of the continuous failed uploads or downloads when one of the servers is out of service but another one can handle the request.

---

Thanks all for the (as usual) knowledgeable information. I think I will go ahead and upgrade for the libcurl fix for myself and the "don't pound the servers" for the good of the project.

---

"Life is a tragedy for those who feel, and a comedy for those who think."

"I never get into an argument that I cannot win."

Thanks all for the (as usual) knowledgeable information. I think I will go ahead and upgrade for the libcurl fix for myself and the "don't pound the servers" for the good of the project.

Remember that the libcurl fix first appeared in v6.10.22 - but that version was a no-no for other reasons.

If the purpose of upgrading is libcurl, you're pretty much limited to v6.10.25 or v6.10.32 - and there's a general bug in the entire v6.10.xx range, fixed but not yet deployed, so v6.10.32 won't be the end of the development line. (Just don't use <ncpus>0</ncpus> - that's the only problem I know of).

Thanks all for the (as usual) knowledgeable information. I think I will go ahead and upgrade for the libcurl fix for myself and the "don't pound the servers" for the good of the project.

Remember that the libcurl fix first appeared in v6.10.22 - but that version was a no-no for other reasons.

If the purpose of upgrading is libcurl, you're pretty much limited to v6.10.25 or v6.10.32 - and there's a general bug in the entire v6.10.xx range, fixed but not yet deployed, so v6.10.32 won't be the end of the development line. (Just don't use <ncpus>0</ncpus> - that's the only problem I know of).

I've had v6.10.25 on most of my machines for a while. It is a pretty stable release IMO.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the BP6/VP6 User Group today!

Good morning all...

There is an email coming to many Boinc users. A survey but they want your email and passwords...DON'T GIVE THEM THAT---DIRECTOR DR. ANDERSON NEEDS TO LOOK AT THAT; HE SIGNED IT...I AM SUSPICIOUS...I WILL NOT GIVE THAT INFO; SETI ALREADY HAS THAT INFO...

SOMEONE NEEDS TO ADDRESS THIS RIGHT AWAY BEFORE PEOPLE FALL FOR IT. IF IT IS REAL, IT IS DONE VERY POORLY!

Best,

mizzou

---

Robert L. Hanson, Ed.D.

Good morning all...

There is an email coming to many Boinc users. A survey but they want your email and passwords...DON'T GIVE THEM THAT---DIRECTOR DR. ANDERSON NEEDS TO LOOK AT THAT; HE SIGNED IT...I AM SUSPICIOUS...I WILL NOT GIVE THAT INFO; SETI ALREADY HAS THAT INFO...

SOMEONE NEEDS TO ADDRESS THIS RIGHT AWAY BEFORE PEOPLE FALL FOR IT. IF IT IS REAL, IT IS DONE VERY POORLY!

Best,

mizzou

I would think something of this nature might be worthy of it's own post, rather then a comment in an unrelated thread.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the BP6/VP6 User Group today!

, Ed.D.

I would think something of this nature might be worthy of it's own post, rather then a comment in an unrelated thread.

I work at a university and my experience with Doctors of Education is that they typically don't display even a modicum of common sense. :)

Apologies in advance to Dr. Hanson for the semi-joke at his expense.

---

"Life is a tragedy for those who feel, and a comedy for those who think."

"I never get into an argument that I cannot win."