low RAC with RX 570 card?
7 Jan 2022 13:49:28 UTC
Topic 226724
(moderation:
Hi all, I have a RX 570 card that turns in very low RAC (1,652) compared to even a 1050 Ti (56,625)
Does this seem right? different hosts but similar CPU and OS
Gravitational Wave search O3 All-Sky #1 v1.01 () windows_x86_64 tasks
melk wrote:Hi all, I have a
)
A 570 has 5095 fp32gflops 318 fp64gflops and most importantly the FP64 = 1/16 FP32 ratio
while the 1050Ti has 2138 fp32gflops 66 fp64 gflops and again most importantly a FP64 = 1/32 FP32 ratio
data from here: https://www.geeks3d.com/20140305/amd-radeon-and-nvidia-geforce-fp32-fp64-gflops-table-computing/
melk wrote:Does this seem
)
No, something is drastically wrong with the hardware/software setup for that machine.
Tasks are taking something like 20 times longer than they should. The funny thing is that tasks are validating so that sort of hints at some incredibly low core speed for the GPU or some sort of GPU throttling or over-committing.
Have you checked for heat issues? Are the GPU's fans running correctly? Are you running something compute heavy on all the available CPU threads? Your tasks list shows only GW GPU tasks. Maybe you're running other projects? Are you running multiple concurrent GPU tasks? Have you updated hardware or software on that machine recently?
Unfortunately, something is wrong with your setup and you'll just have to find what it is. If it was a task problem, they wouldn't be validating.
Cheers,
Gary.
Gary Roberts wrote:...Tasks
)
But as of 6 Jan, Melk's tasks are completing in the expected time range, so that RAC should tick up in the coming week. Glad to see things are running well now! What did you change Melk?
What seems odd now though is the relatively long CPU time for each task. My RX570s run GW tasks with CPU times about 1/3 of completion times, but Melk's CPU times are closer to 3/4 of completion times. That's not a problem per se, but I can't think of why there would be a difference.
Ideas are not fixed, nor should they be; we live in model-dependent reality.
cecht wrote: What seems odd
)
possibly due to differences in CPU speed/IPC (as GW tasks are fairly CPU bound, a slow CPU slows down overall computation) and or differences in "multiplicity", or a combination of the two, or more (other CPU loads, environmental differences, etc), factors.
_________________________________________________________________________
Based on current tasks and
)
Based on current tasks and processing speeds your rx 570 should top out at over 50,000 RAC.
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Well it must have been some
)
Well it must have been some sort of glitchy driver issue, as I did a "clean install' of the most recent version and immediately my RAC has jumped up for that card.
Thanks all for taking a look. I wish I would have realized sooner, I've been running this box for quite a while.
I do run CPU tasks on the host as well, but generally have boinc client set to use 75% of available cpu in order to leave room for GPU overhead and such.
RAC still climbing, about to
)
RAC still climbing, about to crack 45k :)
That said, anyone else notice that during processing the O3AS tasks seem to stall out at 99% with no gpu load. They eventually do finish and validate but there's long chunks of time where the gpu is idle and boinc client reports the tasks at 99%. I've observed this same behavior on multiple hosts with different gpu's.
melk wrote: RAC still
)
yes that's normal for the gravitational wave tasks. I believe the final step is doing some CPU processing so it takes longer.
_________________________________________________________________________
You can run the GWs 2X on
)
You can run the GWs 2X on that card. Then stagger the start times and the GPU will always have something to do. By doing that my GTX1660s processes apx. 15 to 20% more work.