Posts by BobCat13

1) (Message 1825)
Posted 29 Sep 2013 by BobCat13
Post:
The BOINC server tries to work out which app is faster. It does that by trying a number of work units using each app. Once its got an idea how long they take it can then give you work for the fastest app.

I got some vanilla 101 as well as the SSE2 and SSE3 versions when the 101 app was first released. While they can be annoyingly slow (well the vanilla app was) if you just let them run the server will quickly work out what is best for your machine.

I don't understand why the Windows 64-bit and Linux 64-bit applications even have a vanilla version, as 64-bit CPUs have SSE2 at minimum. It would seem that the vanilla version could be removed and just go with the SSE2, SSE3, and AVX versions for 64-bit.
2) (Message 526)
Posted 30 Dec 2012 by BobCat13
Post:
BobCat13 wrote:
They will get sent, eventually. It seems on a lot of new projects resends are added to the end of the queue instead of being added to the beginning. There is a configuration option for the server about resends.

Here is the page about resends: Project Options
Looks like it is under the section Accelerating retries, option <reliable_priority_on_over>X</reliable_priority_on_over>


Did some more reading, and the feeder has some command-line options also:
Backend Programs

The --priority_order_create_time looks interesting. If I interpret that correctly, then it moves higher priority jobs to the front of the queue in the order that the resends were created, so older resends before newer resends. If no resends are available, then it should distribute work based on task creation order.
3) (Message 209)
Posted 8 Sep 2012 by BobCat13
Post:
7.0.24 from the repo causes errors. You will need a newer version. Here is a link to a BoincStats thread that contains some more info:

http://boincstats.com/en/forum/9/7346,1
4) (Message 105)
Posted 14 Jul 2012 by BobCat13
Post:
My machine has had 8 tasks error due to the signal 11. All of them were due to DNS resolution problems from my provider, resulting in the dreaded no heartbeat error between client and sciences.

The T4T VM not starting correctly may have caused the no heartbeat as well. Asteroids@home tasks don't recover gracefully from no heartbeat errors, it would seem.
5) (Message 73)
Posted 28 Jun 2012 by BobCat13
Post:
They will get sent, eventually. It seems on a lot of new projects resends are added to the end of the queue instead of being added to the beginning. There is a configuration option for the server about resends.

Here is the page about resends: Project Options
Looks like it is under the section Accelerating retries, option <reliable_priority_on_over>X</reliable_priority_on_over>