LHC@home

Hello,

I have a WU (n° 16109076) which take 18 houres for 1.000.000 turns using SixTrack 4.67 ... I think it\'s not normal, is it ?

For the other tasks, it take normally not more than 4 hours (for 1.000.000 turns).

Bye

Your floating points scores aren\'t particularly impressive.

Floating Point = 934.86 million ops/sec
MIPS = 2048.08 million ops/sec

A computer with the same task, which did it in a third of the time had 3 times the CPU performance

Floating Point = 2931.25 million ops/sec
MIPS = 7365.98 million ops/sec

The T model Core Duo processors are designed for low wattage efficient performance. Running at ~85W your laptop has a 6th the power of my desktop. Your other computer would have done it twice as fast.

Rob

Thank\'s Rob.

But comparing to myself, it was anyway much more longer.

My score is not faramonus because it\'s a portable computer always on \"power save\" :D

I had 2 WU\\\\\\\'s finish so far and they both were \\\"Aborted by project\\\"; why is this? Will I still get whatever credit(s)?

---

\"Aborted by project\"; why is this?

I can not answer with certainty about the credit story, I will leave this for someone else to answer.

The \"why\" question is easier to answer: every work unit is sent out immediately 5 times. Every time is one task. The moment 3 tasks are returned with identical results the other 2 tasks around get canceled. This is what happened with your 2 tasks. 3 others also had your Work Unit but were faster returning the result.

Depending on the speed of your computers you can count on an average of 40% (2 out of 5 tasks) that will get canceled at some time. If you want to be more certain that you actually can crush the tasks that are allotted to you, then the best way is to keep your queue as short as possible. This way you get constantly tasks from \"fresh\" Work Units, with less chance that others are faster. Or with bigger chance that their tasks are somewhere down their queue.

I had 2 WU\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'s finish so far and they both were \\\\\\\\\\\\\\\"Aborted by project\\\\\\\\\\\\\\\"; why is this? Will I still get whatever credit(s)?

It is not quite as simple as rembertw said.

Each WU is sent out to 5 people and once 3 identical replies have been received, an abort order is sent out to anyone who they don\\\'t know as having started the WU. The idea is so that you can move onto a more productive WU.

Unfortunately they don\\\'t know that a WU has started unless you have had a project update since it was started. You will not get any credits for those WUs. If they know that someone has started the WU, they are allowed to continue and get the credit.

Many people have their computers on permanently and have a high resource share for LHC@home, so they pick up the WUs as soon as they become available and start crunching immediately. Many WUs also finish very quickly so it can be that the Abort message is issued only half an hour after the WU has been issued.

If it was aborted by the project, it hadn\'t started running yet. So, there is no credit to lose.

---

Click here to see My Detailed BOINC Stats

If it was aborted by the project, it hadn\\\'t started running yet. So, there is no credit to lose.

There are some which slip through the net. If a WU has started but there hasn\'t been an update since it started, then it can still abort because the project doesn\'t know it that it has started. Or it may be the BOINC Platform rather than the project. Either way, hit the update and it doesn\'t abort.