Much as I like to accumulate credit for work done, 1.18 is giving way too much - it would make QMC or Cosmo blush ;)

As and when 1.19 comes along for x86 32bit can we have twice as much work per unit, or perhaps halve the 6.5 fixed credit? I'd prefer the former as the WUs are now rather short - Only 9 minutes on my ancient Celeron 2.93.

I'm not worried about the progress indicator (the WUs are short enough not to worry), but is the 'freezing' problem fixed? Haven't had a frozen WU for a while, but I won't crunch Milkyway when I'm away from the machines in case I get a freezer and waste valuable crunching time :)

Al.

Much as I like to accumulate credit for work done, 1.18 is giving way too much - it would make QMC or Cosmo blush ;)

As and when 1.19 comes along for x86 32bit can we have twice as much work per unit, or perhaps halve the 6.5 fixed credit? I'd prefer the former as the WUs are now rather short - Only 9 minutes on my ancient Celeron 2.93.

I'm not worried about the progress indicator (the WUs are short enough not to worry), but is the 'freezing' problem fixed? Haven't had a frozen WU for a while, but I won't crunch Milkyway when I'm away from the machines in case I get a freezer and waste valuable crunching time :)

Al.

We added code that should let us find the freezing problem. Basically you can add a function which will spit out what is causing the crash -- so once we get some workunits that have frozen again we should be able to debug and fix that.

---

We added code that should let us find the freezing problem. Basically you can add a function which will spit out what is causing the crash -- so once we get some workunits that have frozen again we should be able to debug and fix that.

Dang ! Almost got a heart attack !!! reading "freezes etc" ...

Hmm ok ... seems to work for you :)
@All ....
Credit is not the issue atm .. getting all apps properly working is WAY more important now.

Thanks you.

---

Join Support science! Joinc Team BOINC United now!