Ouch! New workunits take three times more time and give NO credit

[michael37]

I just ran into a few MB(?) workunits with AR ~1.48 which take EXCEEDINGLY long amount of time and produce literally no credit.  Ouch, that hurts!  Is that normal?  What's going on???

Here is a workunit that took 30,000 seconds.  For comparison, a normal 0.42 linefeed workunit takes about 8000 seconds to crunch on this computer.

Code: [Select]

CPU time 30737.35721
stderr out

<core_client_version>5.8.16</core_client_version>
<![CDATA[
<stderr_txt>
Optimized SETI@Home Enhanced application
Optimizers: Ben Herndon, Josef Segur, Alex Kan, Simon Zadra
Linux port: Crunch3r, Hans Dorn, Simon Zadra
   Version: Linux 64-bit based on S@H V5.15  'Noo? No - Ni!'
  Revision: R-2.4|xP|FFT:IPP_SSE3|Ben-Joe
     CPUID:                   Intel(R) Xeon(TM) CPU 2.80GHz
      CPUs: 2, cores: 1,  cache: L1=16K,  L2=1024K, L3=0K
  Features: MMX  SSE  SSE2  SSE3  x86_64
     Speed: 2800 MHz

Work Unit Info
True angle range:  1.486459
Optimized SETI@Home Enhanced application
Optimizers: Ben Herndon, Josef Segur, Alex Kan, Simon Zadra
Linux port: Crunch3r, Hans Dorn, Simon Zadra
   Version: Linux 64-bit based on S@H V5.15  'Noo? No - Ni!'
  Revision: R-2.4|xP|FFT:IPP_SSE3|Ben-Joe
     CPUID:                   Intel(R) Xeon(TM) CPU 2.80GHz
      CPUs: 2, cores: 1,  cache: L1=16K,  L2=1024K, L3=0K
  Features: MMX  SSE  SSE2  SSE3  x86_64
     Speed: 2800 MHz

Work Unit Info
True angle range:  1.486459
SETI@Home Informational message -9 result_overflow
NOTE: The number of results detected exceeds the storage space allocated.

Spikes Pulses Triplets Gaussians Flops
   0     31       0        0     134272140666

</stderr_txt>
]]>

Validate state Initial
Claimed credit 0.442911575113843
Granted credit 0.442911575113843
application version 5.21

Links to workunits:
http://setiathome.berkeley.edu/result.php?resultid=591511765
http://setiathome.berkeley.edu/result.php?resultid=591511775
http://setiathome.berkeley.edu/result.php?resultid=590794475

[Richard Haselgrove]

Read the latest technical news:

http://setiathome.berkeley.edu/forum_thread.php?id=41585&nowrap=true#620572

There was a batch of bad WUs split. Not your problem, not Simon's problem. Oh, and there are other threads reporting this, both here and at SETI.

[michael37]

Cool, thanks.   I guess the language of everyone who describes the problem is different so it's hard to find matches in forums.