7 from the 11th and 16 from today ;o)

---

Now that was a run and my 2 rigs managed to grab 32 of those critters today.

Cheers.

46 so far today...

---

Sigh - seems I get a few now and again, but not many. And of those I've recently gotten about 25% are "junk" that finish in a couple of seconds, then report too much RFI. But the good ones do process in about 20 minutes each on my video card :-) or about 4-1/2 hours when I get CPU (SSE) Astropulse units :-|

Now if there was a way to get enough of ANY kind of unit to keep my GPU busy all day on Tuesday "blackouts", that would REALLY be nice. (Yeah, no -- I'm not really interested in doing other BIONC projects. Been sticking with SETI@home for, what, nearly 19 years now. Not really interested in any of the other projects.) Oh well. At least my GPU is busy for most of the 24/7 it's available to look for E.T.

---

Only a few received here have been "noise bombs" (or highly blanked) and 6 have been delivered here since the servers came back online.

Though it would be very nice to get enough GPU work to last a day at least.

Cheers.

Only a few received here have been "noise bombs" (or highly blanked) and 6 have been delivered here since the servers came back online.

Though it would be very nice to get enough GPU work to last a day at least.

Cheers.

I'm still wet behind the ears here, "Noise Bombs" is that excessive signals? if so had a few also..

Only a few received here have been "noise bombs" (or highly blanked) and 6 have been delivered here since the servers came back online.

Though it would be very nice to get enough GPU work to last a day at least.

I'm still wet behind the ears here, "Noise Bombs" is that excessive signals? if so had a few also..

Noise Bombs wind up with 30/30 overflow results while "Highly Blanked" ones will tell you that. ;-

Cheers.

Only a few received here have been "noise bombs" (or highly blanked) and 6 have been delivered here since the servers came back online.

Though it would be very nice to get enough GPU work to last a day at least.

I'm still wet behind the ears here, "Noise Bombs" is that excessive signals? if so had a few also..

Noise Bombs wind up with 30/30 overflow results while "Highly Blanked" ones will tell you that. ;-

Cheers.

Yes had a couple of them, "highly blanked" ? guess I'll work it out :P

Now if there was a way to get enough of ANY kind of unit to keep my GPU busy all day on Tuesday "blackouts", that would REALLY be nice. (Yeah, no -- I'm not really interested in doing other BIONC projects. Been sticking with SETI@home for, what, nearly 19 years now. Not really interested in any of the other projects.) Oh well. At least my GPU is busy for most of the 24/7 it's available to look for E.T.

There are several ways to bypass the Boinc 100 WU limitation but all are controversial and speak about them is like throw gasoline into fire.
FYI this are some of the ways:
- Go to the Boinc code and fake the numbers of GPU's. That will give 100WU per fake GPU added.
- Run several instances of Boinc in your host. Each instance adds his own 100 WU limit.
- The most explosive of all IMHO, Bunkering or rescheduling.
Be aware to use any of them, you need to be an advanced user who really knows what you are mess with.
The 100 WU limit was introduced few years ago to keep the DB smaller and stable.
You have a 1060 GPU the 100 GPU WU limit gives you about a day of work so IMHO not believe you really need to go to this extreme actions.
Fast Linux boxes & users with high end GPU's are more likely need to use this bypasses to keep their hungry hosts feeded during the outages.

---

I get 2 GPU Astropulse WU and 1 Monster CPU WU. The biggest Wu, that i have crunched now...

...
You have a 1060 GPU the 100 GPU WU limit gives you about a day of work so IMHO not believe you really need to go to this extreme actions.
Fast Linux boxes & users with high end GPU's are more likely need to use this bypasses to keep their hungry hosts feeded during the outages.

If working on AP units (@ about 20 min. each), 100 per day would be more than enough. However, for non-AP units the average run time for GPU tasks is right about 5 minutes each. I run two tasks concurrently, so the reported typical ~600 second "run time" on completed units in my stats has to be essentially cut in half. Those are very much by far the most common GPU tasks I get and the 1060 reliably grinds through about 250+ of those a day. Those with more capable cards (like a 1080) could expect about double that throughput.

---

...
You have a 1060 GPU the 100 GPU WU limit gives you about a day of work so IMHO not believe you really need to go to this extreme actions.
Fast Linux boxes & users with high end GPU's are more likely need to use this bypasses to keep their hungry hosts feeded during the outages.

If working on AP units (@ about 20 min. each), 100 per day would be more than enough. However, for non-AP units the average run time for GPU tasks is right about 5 minutes each. I run two tasks concurrently, so the reported typical ~600 second "run time" on completed units in my stats has to be essentially cut in half. Those are very much by far the most common GPU tasks I get and the 1060 reliably grinds through about 250+ of those a day. Those with more capable cards (like a 1080) could expect about double that throughput.

If that is your case you could try to use one of the options to bypass the 100 WU limitation i talk about, they work with AP and/or MB WU.
The easiest and maybe the most controversial one to try is the last one, bunkering or rescheduling, there are few threads about that in the NC forums. You will notice there are many ways to do that, I suggest you read the forums, make your choice and follow the trails. Sure you will obtain some help there if you have any questions.

---

The dangerous part of rescheduling or bunkering is that if the rescheduled tasks sit in the 'other' task type cache and get crunched there, they can then be susceptible to being errored out due to "task time exceeded" from the application of rsc_fpops calculation because the computer and BOINC is unaware the task has moved task type. Rescheduling should only be used on fast crunchers to get through the Tuesday outage.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

10 turned up here overnight.

Cheers.

Woo hoo - just noticed that I have eight in my current queue. Seven for the GPU and one CPU version (SSE2).

---

Nada

---

6 fresh 1's greeted me here this morning.

Cheers.

only two yesteday and two this night ;)

---

8 fresh 1's and 3 resends so far for today.

Cheers.

8 fresh 1's and 3 resends so far for today.

The final count for the 17th March UTC was 13 fresh jobs and 3 resends.

Cheers.