Over the many years that this search has been running, there have sometimes been either increases or decreases in the run time between different batches. What you are seeing is not particularly unusual.
Over the many years that this search has been running, there have sometimes been either increases or decreases in the run time between different batches. What you are seeing is not particularly unusual.
Indeed, when I was running FGRP5 on my C2D, some tasks needed just 13-14k CPU seconds, some needed over 60k.
I don't know if I am still working through older work units or something, but before the new work started I was averaging 2.5 hours per unit, and when the switch happened, I went to averaging 8 hours per unit. I was waiting to see if it would get faster over time, but it still hasn't for me.
It doesn't matter so much that it takes a long time, but for the same credit as before they aren't very productive.
Just to say: more FGRP5 data
)
Just to say: more FGRP5 data is being prepared, should only be a matter of days. The search is far from over.
BM
It looks like the new tasks
)
It looks like the new tasks “Gamma-ray pulsar search #5 v1.08 () windows_intelx86” take ~ 2 times longer to finish. Does anybody see this too?
TRAPPIST-713 wrote: It looks
)
Same here, under Linux.
Mine, too. Running MacOS.
)
Mine, too. Running MacOS. Hope this doesn't last too long.
Plus SETI Classic = 21,082 WUs
So, then the question is if
)
So, then the question is if this additional work time is useful or if this is just a bug in the new batch of tasks.
Over the many years that this
)
Over the many years that this search has been running, there have sometimes been either increases or decreases in the run time between different batches. What you are seeing is not particularly unusual.
Cheers,
Gary.
Gary Roberts wrote:Over the
)
Indeed, when I was running FGRP5 on my C2D, some tasks needed just 13-14k CPU seconds, some needed over 60k.
.
Thanks for the report. We are
)
Thanks for the report. We are re-generating the new batch of work with shorter runtimes and will switch to it as soon as it is ready.
BM
It took us a little longer
)
It took us a little longer than expected, but the FGRP5 tasks that are produced now should be back to earlier runtimes,
BM
I don't know if I am still
)
I don't know if I am still working through older work units or something, but before the new work started I was averaging 2.5 hours per unit, and when the switch happened, I went to averaging 8 hours per unit. I was waiting to see if it would get faster over time, but it still hasn't for me.
It doesn't matter so much that it takes a long time, but for the same credit as before they aren't very productive.