My RX 570 Linux host has completed 3 BPR7 tasks today in 25 sec to 59 sec (running at 1X). My RX5600XT host has been working on one task for 3hr 45m, and is 90% complete. Hmmmm.
Ideas are not fixed, nor should they be; we live in model-dependent reality.
My RX 570 Linux host has completed 3 BPR7 tasks today in 25 sec to 59 sec (running at 1X). My RX5600XT host has been working on one task for 3hr 45m, and is 90% complete. Hmmmm.
So they run on cpu's too? I can do that even if it takes that long!!
My RX 570 Linux host has completed 3 BPR7 tasks today in 25 sec to 59 sec (running at 1X). My RX5600XT host has been working on one task for 3hr 45m, and is 90% complete. Hmmmm.
So they run on cpu's too? I can do that even if it takes that long!!
no, these are not CPU tasks, and will likely never be CPU tasks. BRP4/G are going to be used for CPU. BRP7 is for GPUs
they only have apps for AMD and Nvidia GPUs. an RX5600XT is an AMD GPU. cecht is commenting that it's odd that his 5600XT GPU is taking so long.
Doh, none my GPUa are attached to Linux machines. I will see if I can switch around OSes or GPUs in a few days but I may just need to wait until the tasks are available for Windows.
I got a few MeerKAT M22 tasks for NVidia GPU under Windows. Short deadline, but they won't run immediately with my current settings. I'll push them through after lunch, and see what happens.
is the app really a cuda55 app? why such an old cuda version? depending on how it was built, it might not support the newer GPUs unless you built with a much newer CUDA version (11.4+)
First task 1331624228 failed with a Microsoft 0xc0000135 error - that's a missing DLL.
Looking at the app with the 64-bit dependency walker, it's expecting cudart64_55.dll and cufft64_55.dll, wheras the circulated files are cudart_xp64_55_22.dll and cufft_xp64_55_22.dll
That could be cured via a rename in the <app_version> - I'll try that later. (machine is Windows7/64)
Edit - dependency walker is happy with the rename. Now to try it for real.
And run Linux. Since the
)
And run Linux. Since the application seems to be Linux only right now.
_________________________________________________________________________
My RX 570 Linux host has
)
My RX 570 Linux host has completed 3 BPR7 tasks today in 25 sec to 59 sec (running at 1X). My RX5600XT host has been working on one task for 3hr 45m, and is 90% complete. Hmmmm.
Ideas are not fixed, nor should they be; we live in model-dependent reality.
cecht wrote: My RX 570 Linux
)
So they run on cpu's too? I can do that even if it takes that long!!
mikey wrote:cecht
)
no, these are not CPU tasks, and will likely never be CPU tasks. BRP4/G are going to be used for CPU. BRP7 is for GPUs
they only have apps for AMD and Nvidia GPUs. an RX5600XT is an AMD GPU. cecht is commenting that it's odd that his 5600XT GPU is taking so long.
_________________________________________________________________________
Doh, none my GPUa are
)
Doh, none my GPUa are attached to Linux machines. I will see if I can switch around OSes or GPUs in a few days but I may just need to wait until the tasks are available for Windows.
There are now App versions
)
There are now App versions for Windows 64, CUDA and OpenCL/AMD.
We didn't build and deploy CUDA App versions for ages (the last build I found was from 2015), it might not go flawlessly on the first attempt.
BM
I got a few MeerKAT M22 tasks
)
I got a few MeerKAT M22 tasks for NVidia GPU under Windows. Short deadline, but they won't run immediately with my current settings. I'll push them through after lunch, and see what happens.
is the app really a cuda55
)
is the app really a cuda55 app? why such an old cuda version? depending on how it was built, it might not support the newer GPUs unless you built with a much newer CUDA version (11.4+)
_________________________________________________________________________
Got 9 BRP7 CUDA tasks, all
)
Got 9 BRP7 CUDA tasks, all errored out immediately. Maybe CUDA version(5.5?) is too old for mRTX3070 to run.
First task 1331624228 failed
)
First task 1331624228 failed with a Microsoft 0xc0000135 error - that's a missing DLL.
Looking at the app with the 64-bit dependency walker, it's expecting cudart64_55.dll and cufft64_55.dll, wheras the circulated files are cudart_xp64_55_22.dll and cufft_xp64_55_22.dll
That could be cured via a rename in the <app_version> - I'll try that later. (machine is Windows7/64)
Edit - dependency walker is happy with the rename. Now to try it for real.