LHC@home

For the last few hours, one of my machines has been processing sixtrack 4.67 WUs in 73 seconds - one after another - it goes to 99.6% complete after first 5 seconds, then crawls (!) up the rest in the next minute. Meantime, the other "processor" is chewing along as normal.

The Results table show the WU as being perfectly OK - no mention of computation errors.

I realise that there may be some condition checking which decides that this chunk of data isn't worth analysing - but how come this is on every WU I'm getting right now?

---

<img src="http://seti.mundayweb.com/stats.php?userID=903"><br>
<img src="http://boinc.mundayweb.com/one/stats.php?userID=2034">

OK problem solved - but someone may want to take note

I rebooted machine - one of the slots had to be manually 'End Now'.

Now it's back to normal.

So something had put that slot into a funny state. Suppose I hadn't noticed - guess the daily limit check would have kicked in.

---

<img src="http://seti.mundayweb.com/stats.php?userID=903"><br>
<img src="http://boinc.mundayweb.com/one/stats.php?userID=2034">