Jake -

Just tried a "user update" and got another 30 tasks.

And still, every time I complete a task and try to "replace it", no tasks are down loaded.

Vortac and wb8ili,

Is this the case for every request? What is the most workunits you have received from a request? Our current configuration settings allow for 600 download per request so I'm trying to pinpoint where this error is occurring.

Best,
Jake

It seems like I can't get any work until my queue runs completely dry and then I'll download 200 more tasks. Those 200 will complete and the queue will continue to drop. Tasks are being reported immediately but no tasks are downloaded to keep the queue topped off. If I try to manually update I'm just told the last request was too recent. That continues until everything is gone, I run a couple of tasks from a backup project and then I can update to get 200 more tasks. The older server would keep tasks at 80 pretty much at all times without user intervention.

Hey Everyone,

I implemented a fix to the BOINC stats exporting. This can take up to 24 hours to propagate through so I'll check on it tomorrow.

Best,

Jake

>>> All the questions here have answers in other threads.

What you say there is possibly true, but if, as I, you are connected to many projects, reading all threads on all forums at all projects would take more than a day per day.

The solution for me, is to reduce the number of projects I support, the ones I drop first are the ones that "irritate".

looks like it's working now, i'm gettimg the same credit I got before the problem.
is there anyway to go back and give credit to all the 0 credit results?

I think I found the issue with the credit assignment. It seems that the newest BOINC server version no longer supports how we would set the credit per workunit. Should be a pretty easy fix, I am working on an implementation now.

Best,

Jake

There are still 170k workunits outstanding (on people's computers getting crunched.) Sorry if it wasn't clear, but this was what I was trying to minimize.

Best,
Jake

@BeemerBiker: There is thread somewhere about Nvidia Titan V running MH. In that thread, the author mentions about each WU uses about 1.5GB of VRAM. So you can run about 6 WUs on a S9100 (12GB) or 8-10 WUs on S9150 (16GB).

As for compiling, here is roughly how I do it in Linux:
https://gist.github.com/neofob/8a73e2f44787541c11c0445763953950

are these runs way longer ?? I went from running 2 gpu units at 3 minutes to running hours and barly hitting the GPU

We need a bigger limit allowed for WUs in progress for GPUs with this daily database issue. 600 doesn't cut it with multiple Tahiti based GPUs in 1 PC.

You could reconfigure BOINC to say you have more GPUs than you actually do. Some SETI users do that since there is a weekly server maintenance.
https://setiathome.berkeley.edu/top_hosts.php

[63] NVIDIA GeForce GTX 1080 Ti (4095MB) driver: 410.66

[64] NVIDIA GeForce GTX 1070 (4095MB) driver: 415.27

[64] NVIDIA TITAN V (4095MB) driver: 410.57 OpenCL: 1.2

Doesn't work anymore so much. 200 per GPU up to 600 mad per host, it will only care about 3 of those fake GPUs. Used to be able to get around 1100 or more.

Longer WUs for GPUs with a matching credit adjustment sounds like a good plan. Server getting beat up constantly from these short request times (1m30 between reguest in BOINC) can't be good on top of that.