I spoke too soon -- in Windows Task Manager, it appears that Prime95 never exceeds ~48% CPU usage if BOINC is running. I get how due to the vagaries of Windows, giving Prime95 a priority of 10 doesn't result in it getting any more cycles, but none of the available settings in Prime95 or BOINC seem to alter the fact that Prime95 won't utilize more than half of available processor time if BOINC is running. I tried giving BOINC just 1 thread and 1% of available CPU time and I tried giving it all 8 threads and 100% of CPU time; processor utilization varies, but rarely approaches the over 90% it does running Prime95 alone. HWInfo shows my GPU utilization at 100% (though Task Manager seems to think the GPU is idle). I'm still looking for a means of getting SRBase to use my GPU without (significantly) interfering with Prime95.

Before jumping to the 72-73 bits range here’s an interesting sub project;

-for range lower than 99M clean all up to 73 bits, I believe this can be done in one week.
https://www.mersenne.ca/status/tf/0/0/2/0

yes, but this is reserved by the GPU72 project? I will ask the admin if these are available but will be working on later in the future.

The last batch with around 122k WUs are running now (795M max), no more work left in the 70-71 range. There could be some tests left. I will check this later. The next 71-72 range is planned later today.

You can trick the server by saying you have x amount of GPU’s or CPU’s. You are too naive. If we had 2700 GPU how many wus would we all be doing per day? Make the calculations.

And exactly what is the purpose of doing so? Why not just accept the amount that the server send out?

Doing the last request would actually make it possible to calculate the real ressources we have - now in stead of a very huge production we only have a very huge cue of work waiting to be processed.

Maybe a setting on the server could/should be made to render that possibility IMPOSSIBLE - is that possible Reb?

A note on my third question is that the server has proven reliable enough to sustain the users with enough work even if they have only 20 workunits cued per host.

You are wrong, please think. Your top host does not have 400 GPU’s.
Your output it is not about how much you can queue but how much you can process. Dividing by 20 is wrong.

On Free-dc stats there are 117 active users of 290 = 117 GPUs

Another ressource is the server status, so you can see active users reported a result, last time I have seen 111.

You are wrong, please think. Your top host does not have 400 GPU’s.
Your output it is not about how much you can queue but how much you can process. Dividing by 20 is wrong.

On Free-dc stats there are 117 active users of 290 = 117 GPUs

Not 2700 GPUs but around 100-200 yes...lol

2700 should be correct, there are only 20 WUs max in progress per host.

Can you queue more than 500k wus onto the server or the limitation is on GIMPS side to provide a bigger batch of wus? Just conscience that we will reach a time we will start processing more than 200-300k wus per day, which would be awesome, and therefore time demanding from your side to keep feeding the server on a daily basis. Really looking forward to seeing for 70-71 bits all done the 4M wus.

yes, its planned but it will growing the database very fast, Iam trying to purge things before I backup the database. The main issue is the assignment queue. The more I have in pipeline the more its taking to report results.

For better understanding the next batch will have a better name with current range max. The current batch reached 438M of 1000M max.

Hey Reb. Are you going to feed the TF with more work or you just awaiting the return of last results? TIA.

No, already posted in the work available thread. There is a problem to request new work running into an error. The admin was already informed.