a trivial question garners a trivial response :)

does it solve your problem?

---

re: CPU use for the task, this is easily configured client-side with an app config file, and it will force 1:1 no matter what the project defines. I'd recommend that.

I wasn't asking you for a trivial response. I'm asking the people that create these work units why they don't specify 1 instead of 0.963.

Because the GPUGrid staff don't set that figure. There's an algorithm in the (Berkeley written) BOINC server code which generates the figure to use from a range of outdated, stupid, data.

I discussed this at some length almost three years ago, in https://github.com/BOINC/boinc/issues/2949 - with examples drawn from GPUGrid, among other projects. I think that this was about the point that Berkeley stopped reading a single word of what I write. Someone else can get to grips with it this time.

thanks Richard, I had a thought that it was likely the output of some automated function within BOINC since nearly all projects end up with something like this by default if they don't manually set the figures.

---

Too bad they never worked to implement all or part of Richard's suggestion / GitHub issue. While I don't claim to be able to see the bigger picture in BOINC it sounds like a good path for automated adjustments when new GPU hardware is released.

Bill F

---

In October of 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

I got one WU today (e1a10-ABOU_rnd_ppod_13-0-1-RND2740_2).

Is it normal behaviour that the WU uses more than 7GB of RAM?

I got one WU today (e1a10-ABOU_rnd_ppod_13-0-1-RND2740_2).

Is it normal behaviour that the WU uses more than 7GB of RAM?

Yes.

---

I got one WU today (e1a10-ABOU_rnd_ppod_13-0-1-RND2740_2).

Is it normal behaviour that the WU uses more than 7GB of RAM?

Yes.

Thanks for answering.

What is typical run time for these tasks? I am at 1 day and x hours processing and only 34% of the way done. I have 2 days left before deadline. I am running a GTX 1080 plain, not TI that is OC'd a bit.

What is typical run time for these tasks? I am at 1 day and x hours processing and only 34% of the way done. I have 2 days left before deadline. I am running a GTX 1080 plain, not TI that is OC'd a bit.

Your times may be about right. I have a GTX 1060 with 6GB and my times were similar.

This task is giving wild results for its estimated time remaining.

This morning, it was saying over 400 days remaining.

Application Python apps for GPU hosts 4.03 (cuda1131)
Name e23a16-ABOU_rnd_ppod_demo_sharing_large-0-1-RND7660
State Running
Received 6/19/2022 6:33:56 AM
Report deadline 6/24/2022 6:34:02 AM
Resources 0.949 CPUs + 1 NVIDIA GPU
Estimated computation size 1,000,000,000 GFLOPs
CPU time 23:13:06
CPU time since checkpoint 00:02:47
Elapsed time 06:42:45
Estimated time remaining 357d 12:44:26
Fraction done 22.580%
Virtual memory size 5.81 GB
Working set size 1.05 GB
Directory slots/10
Process ID 6376
Progress rate 3.240% per hour
Executable wrapper_6.1_windows_x86_64.exe

I've seen other tasks start out claiming over 300 days remaining, and then finish in between 5 and 6 days.

Is there something wrong in the data sent as task input, or is it the wild first ten tasks for a new application version?

Yup, non beta task but I've seen over 3k day ETAs recently.


Name e23a60-ABOU_rnd_ppod_demo_sharing_large-0-1-RND1212_1

Application Python apps for GPU hosts 4.03 (cuda1131)
Workunit name e23a60-ABOU_rnd_ppod_demo_sharing_large-0-1-RND1212
State Running High P.
Received 6/20/2022 12:17:53 PM
Report deadline 6/25/2022 12:17:53 PM
Estimated app speed 311.15 GFLOPs/sec
Estimated task size 1,000,000,000 GFLOPs
Resources 0.99 CPUs + 1 NVIDIA GPU
CPU time at last checkpoint 05:44:17
CPU time 05:47:46
Elapsed time 02:17:30
Estimated time remaining 2764d,01:55:33
Fraction done 11.890%
Virtual memory size 18,693.93 MB
Working set size 3,824.01 MB

Just ignore the ETA estimates. Garbage data.
The tasks finish fine and well within their deadlines.

Were the very long ETA estimates intended to make GPUGRID Python GPU work run before any GPU work from other BOINC projects? They seem to be very good at doing that.

Note there seems to be no thread for discussing non-beta Python tasks.

Were the very long ETA estimates intended to make GPUGRID Python GPU work run before any GPU work from other BOINC projects? They seem to be very good at doing that.

Note there seems to be no thread for discussing non-beta Python tasks.

No not at all. BOINC just has no mechanism for dealing with hybrid cpu-gpu tasks.

The Python on GPU tasks are the first of their kind.

It will take the BOINC devs a lot of time to accommodate them correctly.

If they are getting in the way of your other work, I suggest stopping them or limiting them to only a single task at any time by changing your cache size to absolute minimal values.

Were the very long ETA estimates intended to make GPUGRID Python GPU work run before any GPU work from other BOINC projects? They seem to be very good at doing that.

Note there seems to be no thread for discussing non-beta Python tasks.

The other threads are here:
https://www.gpugrid.net/forum_thread.php?id=5323

https://www.gpugrid.net/forum_thread.php?id=5319

FYI, the Python on GPU tasks are the same as the beta Python tasks currently.

Both tasks are using the latest application code.

The devs said they would still keep the beta plan class available, just not in use, for whenever a new application might be developed.

So everyone is getting the standard Python work even if they have beta selected.

Does anybody know how many cpu threads would be ideal to run them efficiently? I gave them 12 threads exclusively but still the task is run primarily on the cpu with my 3070ti kicking in only sporadically for a second or two.

giving it more cores wont necessarily make it run faster. as few as 4 cores per task works fine on my EPYC system. but if you are running other projects on the CPU it will slow them down as the processes compete with each other for CPU time.

by default the program will use however many cores you have and you really can't change this with any BOINC settings.

also I would recommend putting Linux on that system instead of Windows. Linux runs much faster

---

Gotcha! My Linux Laptop finishes them in 10 hours, my much faster Windows PC needs 18! Thanks again Ian & Steve