Given the new limits I backed myself down to 0.25 day + 0.25 additional.
Looks like it will probably settle the Linux boxes at about 150/2150 (CPU/GPU) and 130/1500 and 75/250 for the Win box.
Really needed to back that off, as with 2000 and 3000+ respectively on the linux at 0.50 day + 0.50 additional, boinctasks was starting to see timeouts dealing with the sheer number of tasks.

---

I suddenly got 900 wu i progress. No metioning of it here. Only me? No ghosts as far as I can tell.

---

This was discussed in panic mode thread. Looks like 200 work units for your chip and 400 work units for each GPU you have.

---

A definitive statement has been posted on GitHub:

Eric Korpela wrote:

I was the one who increased the limits. I based it on database I/O rates
which, it seemed could handle the change. Long term the rates don't change
but the DB "in process" lookups take longer. If it becomes an issue I'll
drop them.

Tasks 'out in the field' (not sure if that exactly matches 'in process') is still rising slowly, and has reached 6.93 million: it will be interesting to see how that changes as the new working week starts around the world.

'Results in the field' has now passed 7 million.

Apologies for all the system e-mails you may have received from post moves into this thread...

For anyone running a "spoofed" client, you will of course now get 300x the number of "spoofed" GPUs which may be an overload so may want to reduce the "spoof" number appropriately, ie to one-third what it currently is. The hard limit of 10K platform tasks remains, so I was seeing just under 10,200 tasks (10K GPU + 200 CPU) on my largest host (which incidentally isn't overdoing it; this is about a day's worth.) All of the others I had to reduce appropriately as noted.

---

I UL a new spoofed build with a 30000 WU Buffer.
Remember use such big cachê only If you realy have a Very fast system.
And If you use think about use te mutex to make the lag small as posible.

---

Looks like the GPU limit has been lowered again. I'm getting this:

09.12.2019 23.05.42 | SETI@home | Reporting 14 completed tasks
09.12.2019 23.05.42 | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
09.12.2019 23.05.42 | SETI@home | [sched_op] CPU work request: 2123677.81 seconds; 0.00 devices
09.12.2019 23.05.42 | SETI@home | [sched_op] NVIDIA GPU work request: 941881.19 seconds; 0.00 devices
09.12.2019 23.05.46 | SETI@home | Scheduler request completed: got 0 new tasks
09.12.2019 23.05.46 | SETI@home | [sched_op] Server version 709
09.12.2019 23.05.46 | SETI@home | No tasks sent
09.12.2019 23.05.46 | SETI@home | No tasks are available for AstroPulse v7
09.12.2019 23.05.46 | SETI@home | No tasks are available for SETI@home v8
09.12.2019 23.05.46 | SETI@home | Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them
09.12.2019 23.05.46 | SETI@home | Tasks for Intel GPU are available, but your preferences are set to not accept them
09.12.2019 23.05.46 | SETI@home | This computer has reached a limit on tasks in progress
09.12.2019 23.05.46 | SETI@home | Project requested delay of 303 seconds

---

Think you are correct. I am not getting a 1:1 replacement for work turned in. Any tasks I get are just replacing cpu tasks turned in. The gpu task caches are falling.

---

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

A proud member of the OFA (Old Farts Association)

And RTS has spiked up.

Apologies for all the system e-mails you may have received from post moves into this thread...

+1

No apology needed. You were doing what a moderator does. Bringing order out of a chaotic new topic.

THANK YOU!

Tom

---

A proud member of the OFA (Old Farts Association).

Thanks, Tom. :^)
Edit: Also thanks for the confirmation, Dr. Z. Title and my post updated.

---

Yup, looks like they lowered it to 300 per GPU

---

More confirmation via GitHub:

Eric Korpela wrote:

I've dropped the GPU limit to 300 to keep us below 7M. We'll run it there
for a while.

More confirmation via GitHub:

Eric Korpela wrote:

I've dropped the GPU limit to 300 to keep us below 7M. We'll run it there
for a while.

What kind of "7M" does he mean?

---

7M = 7 million = 7,000,000.

Results out in the field.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

More confirmation via GitHub:

Eric Korpela wrote:

I've dropped the GPU limit to 300 to keep us below 7M. We'll run it there
for a while.

What kind of "7M" does he mean?

What he means is the "results out in the field" and 7M means 7 million. ;-)

Cheers.

Eric Korpela wrote:

I've dropped the GPU limit to 300 to keep us below 7M. We'll run it there
for a while.

I wonder if Eric has increased the limits again because we are currently running at 7.27 million.

---

I wonder if Eric has increased the limits again because we are currently running at 7.27 million.

No changes, it's still 200 for CPU and 300 for GPU's.

Cheers.

The infrequent crunchers or ones that only contact the project every ten days are getting filled up at the new cache levels.

---

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

A proud member of the OFA (Old Farts Association)