Ready-to-send buffer is shrinking & a pretty good rate. Should be out of work ready-to-send in the next 6-8 hours.

---

Grant
Darwin NT

Ready-to-send buffer is shrinking & a pretty good rate. Should be out of work ready-to-send in the next 6-8 hours.

Very much depends what Angle Range the next few tapes were recorded at. 19my13ad, 20my13af, and 25se13ad all look to be shorties - haven't seen any 28mr13ae yet.

But in 8 hours we'll be in maintenance anyway, so it won't matter...

Given the number of shorties we've had lately, some longer running WUs can't be too far away.

---

Grant
Darwin NT

... and 25se13ad all look to be shorties ...

... on my side, they are VLARs ...

__W__

---

_______________________________________________________________________________

... and 25se13ad all look to be shorties ...

... on my side, they are VLARs ...

__W__

I have normals to VLARs for that file here.

Cheers.

Well.. my 10-day cache of APs finally ran dry this morning. Oh well. More will arrive eventually. Might get an odd resend here and there in the meantime.

I'm sitting on one AP, waiting for the wingmate. She/he's got 8 more days until timeout. <yawn>

Slow would be the 7.27 android app on beta currently.

Nnnooooo kkiiiiddddiiiinnnnnnngggggg........

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

Given the number of shorties we've had lately, some longer running WUs can't be too far away.

Glad I have some shorties now, actually...

[edit] I've always wondered what a wingmate was, don't have one, I think.

---

rOZZ
Music
Pictures

Shorties are better than nothing...

---

Given the number of shorties we've had lately, some longer running WUs can't be too far away.

Glad I have some shorties now, actually...

[edit] I've always wondered what a wingmate was, don't have one, I think.

Everybody has one.

Its the other host processing the same workunit your computer does.
Each workunit will be processed at least by 2 computers for validation.

---

With each crime and every kindness we birth our future.

Given the number of shorties we've had lately, some longer running WUs can't be too far away.

Glad I have some shorties now, actually...

[edit] I've always wondered what a wingmate was, don't have one, I think.

Everybody has one.

Its the other host processing the same workunit your computer does.
Each workunit will be processed at least by 2 computers for validation.

Oh, that's what it is, thanx Mike:)

---

rOZZ
Music
Pictures

Oh, that's what it is, thanx Mike:)

This is a WU as completed by you and your "wing-man".
http://setiathome.berkeley.edu/workunit.php?wuid=1429542530

---

Oh, that's what it is, thanx Mike:)

This is a WU as completed by you and your "wing-man".
http://setiathome.berkeley.edu/workunit.php?wuid=1429542530

So the running time of my WU is longer because I have to wait for my wingman...now I understand!

---

rOZZ
Music
Pictures

So the running time of my WU is longer because I have to wait for my wingman...now I understand!

NO - the time to be validated is longer if your wingman completes it after you do... Your runtime purely depends on your machine.

---

So the running time of my WU is longer because I have to wait for my wingman...now I understand!

NO - the time to be validated is longer if your wingman completes it after you do... Your runtime purely depends on your machine.

What about the CPU time? Once you report, the task isn't running anymore? I just wonder what the difference between running time and CPU time is then.

---

rOZZ
Music
Pictures

So the running time of my WU is longer because I have to wait for my wingman...now I understand!

NO - the time to be validated is longer if your wingman completes it after you do... Your runtime purely depends on your machine.

What about the CPU time? Once you report, the task isn't running anymore? I just wonder what the difference between running time and CPU time is then.

Boinc is waiting for the finnish call.

---

With each crime and every kindness we birth our future.

What about the CPU time? Once you report, the task isn't running anymore? I just wonder what the difference between running time and CPU time is then.

The running time is the time that accumulates on your wall-clock while the job is running; the CPU time is the time that the CPU is actually processing the work-unit. CPU time will almost certainly be smaller than run-time[1] because of overheads that the CPU has to process instead of your job while the wall-clock is still ticking. So if you do a lot of other processing, say word-processing or game-playing, your run-time might be considerably greater than the CPU time. An extreme example can be seen with some GPU processing -- the time spent by the GPU isn't counted against CPU time, so if the GPU is doing most of the work the CPU is either idle or doing other stuff so you can have an elapsed time in minutes or hours (however long the GPU took) but CPU time measured in seconds.

[1] If we ever get into multi-threading or other parallelisation techniques, CPU time can exceed run-time because more than one core runs at once. I had an extreme example of that recently when I ran 180 parallel threads at once on a Xeon Phi -- elapsed running time was seven minutes or so, accumulated CPU time was well over twenty hours!

---

What about the CPU time? Once you report, the task isn't running anymore? I just wonder what the difference between running time and CPU time is then.

The running time is the time that accumulates on your wall-clock while the job is running; the CPU time is the time that the CPU is actually processing the work-unit. CPU time will almost certainly be smaller than run-time[1] because of overheads that the CPU has to process instead of your job while the wall-clock is still ticking. So if you do a lot of other processing, say word-processing or game-playing, your run-time might be considerably greater than the CPU time. An extreme example can be seen with some GPU processing -- the time spent by the GPU isn't counted against CPU time, so if the GPU is doing most of the work the CPU is either idle or doing other stuff so you can have an elapsed time in minutes or hours (however long the GPU took) but CPU time measured in seconds.

[1] If we ever get into multi-threading or other parallelisation techniques, CPU time can exceed run-time because more than one core runs at once. I had an extreme example of that recently when I ran 180 parallel threads at once on a Xeon Phi -- elapsed running time was seven minutes or so, accumulated CPU time was well over twenty hours!

Ok, thanx Ivan:)

---

rOZZ
Music
Pictures

All say Heil to CreditNew.

+ 1000

---

Only 60 AP's left to crunch, less than one day worth of crunching. After that it will be all MB. I expect my RAC to drop to 1/3 of what it is now, since MB pays at a level which is ridicoulous.

All say Heil to CreditNew.

At least the negative credit payout was fixed.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Only 60 AP's left to crunch, less than one day worth of crunching. After that it will be all MB. I expect my RAC to drop to 1/3 of what it is now, since MB pays at a level which is ridicoulous.

All say Heil to CreditNew.

Look at the good side, think of all the tapes that will be cleared of MB's and left with only AP's to be created.

---