It really isn't a good idea to look at the credit granted.
2 WUs

Runtime  Credit
270.46   120.02
272.46    70.93

An extra 2 seconds gets 49 less Credits.
:-/

That's Credit Screw for you. :-(

But watch how everyone's RAC goes up while those GBT tasks dry up. ;-)

Cheers.

It really isn't a good idea to look at the credit granted.
2 WUs

Runtime  Credit
270.46   120.02
272.46    70.93

An extra 2 seconds gets 49 less Credits.
:-/

. . Oohh I know! Credit Screw is amazing in its ability to award points inconsistently.

Stephen

:(

The kitties are having an Aericibo party.................
What delightful crunching!

Meeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeow.

---

"Time is simply the mechanism that keeps everything from happening all at once."

look a these one http://setiathome.berkeley.edu/workunit.php?wuid=2382702170

only 16.69 seconds of work but in the detail ...

http://setiathome.berkeley.edu/result.php?resultid=5405894954

have two sessions

Wallclock time elapsed since last restart: 2772.0 seconds

and the last one

Wallclock time elapsed since last restart: 12.7 seconds

bad time report ?

about 46mn ( about 2700 seconds ) is a normal time with my HD7750 ;)

---

That doesn't mean much, the task could have been suspended while other tasks ran, or the computer was shutdown.

One of mine has
Wallclock time elapsed since last restart: 18107.5 seconds

look a these one http://setiathome.berkeley.edu/workunit.php?wuid=2382702170

only 16.69 seconds of work but in the detail ...

http://setiathome.berkeley.edu/result.php?resultid=5405894954

have two sessions

Wallclock time elapsed since last restart: 2772.0 seconds

and the last one

Wallclock time elapsed since last restart: 12.7 seconds

bad time report ?

about 46mn ( about 2700 seconds ) is a normal time with my HD7750 ;)

That's not too good. Worth to observe if it's rare event or frequently occuring one.
Seems this particular task almost finished and then was restarted at 100%.
Can be just coincidence (if rare) or some problems on task finalization(if frequently occuring).
Also, restart wasn't fully correct cause BOINC client lost info about task duration and reported only length of run after restart.

This can be emulated by completing task offline then copying all corresponding files back to BOINC folder.
That way BOINC will restart from last checkpoint (~100%) but will not have any real info about task duration.
Time printed in stderr app's own measurement and has no connection with BOINC's ones.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Well, I do hope that Centurion can get back on his feet.

But, I must admit that the kitties are luvin' this all Aerecibo kibble diet.
Meow!

---

"Time is simply the mechanism that keeps everything from happening all at once."

Enjoy the shorties now because you will have BLC files nipping at your butt for weeks after this!

Enjoy the shorties now because you will have BLC files nipping at your butt for weeks after this!

I would imagine so.
Oh well, fun for now.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Enjoy the shorties now because you will have BLC files nipping at your butt for weeks after this!

. . But hopefully something other than Blc5s :(

Stephen

.

Enjoy the shorties now because you will have BLC files nipping at your butt for weeks after this!

. . But hopefully something other than Blc5s :(

Stephen

.

Stephen may I ask why you are not wanting blc 5s?

---

With no BLC data currently I would imagine the campus bandwidth will be higher than normal. Would be interesting to know how much higher but I think this would be hard to measure

---

Enjoy the shorties now because you will have BLC files nipping at your butt for weeks after this!

. . But hopefully something other than Blc5s :(

Stephen

.

Stephen may I ask why you are not wanting blc 5s?

. . Because they are the gristliest, nastiest Greenbank WUs that take far longer to crunch than anything else. 100% longer than Arecibo tasks and up to 50% longer than other Guppies. And for some reason they are the ones we get the most of :( ...

. . Does that answer your question :)

Stephen

:)

Let´s finish those tapes from Arecibo 2009

---

Enjoy the shorties now because you will have BLC files nipping at your butt for weeks after this!

. . But hopefully something other than Blc5s :(

Stephen

.

Stephen may I ask why you are not wanting blc 5s?

. . Because they are the gristliest, nastiest Greenbank WUs that take far longer to crunch than anything else. 100% longer than Arecibo tasks and up to 50% longer than other Guppies. And for some reason they are the ones we get the most of :( ...

. . Does that answer your question :)

Stephen

:)

Well, I don't know if that is strictly true, but I do know that my 2 machines, which were doing about 50-55K and 70-75K RAC/day , respectively, have bumped up to roughly 75K and 100K the last 3 days after the GBT WUs ran out, and I've gotten only a handful of APs, so that's mostly due to the lack of GBT.

---

Well, I don't know if that is strictly true, but I do know that my 2 machines, which were doing about 50-55K and 70-75K RAC/day , respectively, have bumped up to roughly 75K and 100K the last 3 days after the GBT WUs ran out, and I've gotten only a handful of APs, so that's mostly due to the lack of GBT.

It is the measure of the feeling we have already sensed that GBTs make us sweat more, but bring less credit.
The possible reasons have been discussed here by Raistmer et alii.
Probably, already people using the Linux Special application may have a different feeling.

Crunch on!

It is the measure of the feeling we have already sensed that GBTs make us sweat more, but bring less credit.
The possible reasons have been discussed here by Raistmer et alii.
Probably, already people using the Linux Special application may have a different feeling.

Crunch on!

Well, yeah, and this should have been anticipated by one and all - after all, the current apps were written for Arecibo data, and therefore somewhat "optimized" (by default) for whatever characteristics that data had (at an unconscious level). So the GB data is not "optimal" for the app, and, naturally, has different characteristics, and therefore poorer computing characteristics for the app. The Linux app has been reoptimized for the GB data, and you see what improvements could be made if the Arecibo app had been tuned for GB, which it (seemingly) wasn't, just made to run on the GB data.

Too bad...

---

Enjoy the shorties now because you will have BLC files nipping at your butt for weeks after this!

. . But hopefully something other than Blc5s :(

Stephen

.

Stephen may I ask why you are not wanting blc 5s?

. . Because they are the gristliest, nastiest Greenbank WUs that take far longer to crunch than anything else. 100% longer than Arecibo tasks and up to 50% longer than other Guppies. And for some reason they are the ones we get the most of :( ...

. . Does that answer your question :)

Stephen

:)

Yes that perfectly answers my question. Thank you

---

Stephen may I ask why you are not wanting blc 5s?

. . Because they are the gristliest, nastiest Greenbank WUs that take far longer to crunch than anything else. 100% longer than Arecibo tasks and up to 50% longer than other Guppies. And for some reason they are the ones we get the most of :( ...

. . Does that answer your question :)

Stephen

:)

Well, I don't know if that is strictly true, but I do know that my 2 machines, which were doing about 50-55K and 70-75K RAC/day , respectively, have bumped up to roughly 75K and 100K the last 3 days after the GBT WUs ran out, and I've gotten only a handful of APs, so that's mostly due to the lack of GBT.

. . Hi Cruncher

. . I rest my case :)

Stephen

:)

The kitties are wondering if the GPUs are gonna run outta work if today's outrage is another 8 hour saga.
What with all the Aerecibo shorties in the cruncher's caches.

Meow?

---

"Time is simply the mechanism that keeps everything from happening all at once."