There are lots of "Unsent" V7 6.97 tasks. Why is that? The returned results hangs in limbo for ages, when someone have aborted their tasks, or they have timed out, or errored out, or there is an inconclusive. The tasks are never sent out to a third party.

One example of many that I have. This one have been in limbo since my wingman aborted it on 11 Mar 2012. I have several other:

Workunit 3850195

---

WARNING!! "THIS IS A SIGNATURE", of the "IT MAY CHANGE AT ANY MOMENT" type. It may, or may not be considered insulting, all depending upon HOW SENSITIVE THE VIEWER IS, to certain inputs to/from the nervous system.

There are lots of "Unsent" V7 6.97 tasks. Why is that? The returned results hangs in limbo for ages, when someone have aborted their tasks, or they have timed out, or errored out, or there is an inconclusive. The tasks are never sent out to a third party.

One example of many that I have. This one have been in limbo since my wingman aborted it on 11 Mar 2012. I have several other:

Workunit 3850195

Unsent tasks go to the Back of the Que, there are 153,448 ready to send tasks at the moment (Some will be AP), and because of the limited amount of hosts here it might take a month or more for them to be resent,

Claggy

There are lots of "Unsent" V7 6.97 tasks. Why is that? The returned results hangs in limbo for ages, when someone have aborted their tasks, or they have timed out, or errored out, or there is an inconclusive. The tasks are never sent out to a third party.

One example of many that I have. This one have been in limbo since my wingman aborted it on 11 Mar 2012. I have several other:

Workunit 3850195

Unsent tasks go to the Back of the Que, there are 153,448 ready to send tasks at the moment (Some will be AP), and because of the limited amount of hosts here it might take a month or more for them to be resent,

Claggy

Most unsent AP's get resent fast though. It seems as if this hanging unsent mostly is something that happens with V7 6.97 though. Perhaps most people on Beta have the box for V7 unticked in the SETI@home/AstroPulse Beta preferences page.

Yeah well, it's not important enough to committ suicide over.

---

WARNING!! "THIS IS A SIGNATURE", of the "IT MAY CHANGE AT ANY MOMENT" type. It may, or may not be considered insulting, all depending upon HOW SENSITIVE THE VIEWER IS, to certain inputs to/from the nervous system.

Watch how fast they disappear after Eric starts beta testing the new CUDA app Jason just wrapped up.

Watch how fast they disappear after Eric starts beta testing the new CUDA app Jason just wrapped up.

Yeah, I guess everyone will untick AP 6 then, and the same issue will arise with AP 6 unsents. Everyone wants to be part of the latest, few will stick with finishing what they started.

Sigh, LOL, whatever....

---

WARNING!! "THIS IS A SIGNATURE", of the "IT MAY CHANGE AT ANY MOMENT" type. It may, or may not be considered insulting, all depending upon HOW SENSITIVE THE VIEWER IS, to certain inputs to/from the nervous system.

Well I'll take the first GPU app for OSX. I'm patiently waiting for any type of GPU work. Right now my CPU is off on other projects but I have ticked to use GPU here but get nothing.

Unsent tasks go to the Back of the Que, there are 153,448 ready to send tasks at the moment (Some will be AP), and because of the limited amount of hosts here it might take a month or more for them to be resent,

Claggy

Most unsent AP's get resent fast though. It seems as if this hanging unsent mostly is something that happens with V7 6.97 though. Perhaps most people on Beta have the box for V7 unticked in the SETI@home/AstroPulse Beta preferences page.

Yeah well, it's not important enough to committ suicide over.

Unticking the S@H v7 box isn't needed, the project is clearly sending AP v6 when they're available to hosts with the default (all applications) configuration. I guess the AP tasks have a higher priority setting.

The other part is that the MB splitter tends to produce huge batches of work, often 3 channels worth (~47000 WUs or ~94000 initial replication tasks), and does so before the ready to send gets very low. But the AP splitters are producing WUs in batches of 101 WUs or so, and only do so when there aren't any AP ready to send. So although any AP reissues go to the end of the queue, they get sent before new work is split.

Of course there are times like now, the AP splitters finished the last channel (B6_P1) of the 10dc10af tape file about 28 hours ago so the odds are any request will get MB v7 tasks.

                                                                  Joe