The random long CPU run-times that I reported earlier in the thread, were indeed due a lack of CPU resources available for the GPU tasks. For the last day and a half, I have been running 5x tasks without isolating the tasks to a set number of CPU threads.
The results of running O3AS in an unconstrained environment are more or less directly in line with everything that PUTUTU has posted in this thread. Average run-time per task of 284s, which puts the PPD at >3M per Radeon VII.
With this run of tasks there is enough headroom to run 6x tasks per GPU. Sorry for the earlier noise in the thread, as I was mostly going off of what I had observed from earlier versions of the app which did use more VRAM/task. I just bumped the tasks/gpu up to six and will let that run for the next few days.
The random long CPU run-times that I reported earlier in the thread, were indeed due a lack of CPU resources available for the GPU tasks. For the last day and a half, I have been running 5x tasks without isolating the tasks to a set number of CPU threads.
The results of running O3AS in an unconstrained environment are more or less directly in line with everything that PUTUTU has posted in this thread. Average run-time per task of 284s, which puts the PPD at >3M per Radeon VII.
With this run of tasks there is enough headroom to run 6x tasks per GPU. Sorry for the earlier noise in the thread, as I was mostly going off of what I had observed from earlier versions of the app which did use more VRAM/task. I just bumped the tasks/gpu up to six and will let that run for the next few days.
Congratz and happy to hear that you are able to get your two VII cards working on O3AS! I'm sure there are a lot of VII cards out there (previously used in MW and FGRBP1) that could be put to good use to help to speed up the O3AS search, in particular running on linux which can be pita. Well, I'm hoping that someone here can write up a how-to-guide on setting up AMD driver on linux.
Installing ROCm drivers is fairly straight forward. but you have to be careful with what kernel you're running, and what card you have and what version of ROCm supports your GPU. i think they dropped Vega support from the new versions so you have to use an older one.
Installing ROCm drivers is fairly straight forward. but you have to be careful with what kernel you're running, and what card you have and what version of ROCm supports your GPU. i think they dropped Vega support from the new versions so you have to use an older one.
I knew there was some quirky thing about getting AMD GPUs to run right with their drivers, but I didn't know what the issues were until now. I still don't know if there are any other issues, too.
Did some tweaking/testing on
)
Did some tweaking/testing on the single VII over the weekend. Here is an updated setup. Timestamp: see returned results after Jun 10, 6:00 UTC
Bumped from 5 → 6 tasks per gpu. Vram ~ 13.5GB
Bumped memory clock from 1000 → 1100MHz
Board power draw (peak) ~ 165W → ~180W
Average run time per task ~273s → 253s
The random long CPU run-times
)
The random long CPU run-times that I reported earlier in the thread, were indeed due a lack of CPU resources available for the GPU tasks. For the last day and a half, I have been running 5x tasks without isolating the tasks to a set number of CPU threads.
The results of running O3AS in an unconstrained environment are more or less directly in line with everything that PUTUTU has posted in this thread. Average run-time per task of 284s, which puts the PPD at >3M per Radeon VII.
With this run of tasks there is enough headroom to run 6x tasks per GPU. Sorry for the earlier noise in the thread, as I was mostly going off of what I had observed from earlier versions of the app which did use more VRAM/task. I just bumped the tasks/gpu up to six and will let that run for the next few days.
tictoc wrote:The random
)
Congratz and happy to hear that you are able to get your two VII cards working on O3AS! I'm sure there are a lot of VII cards out there (previously used in MW and FGRBP1) that could be put to good use to help to speed up the O3AS search, in particular running on linux which can be pita. Well, I'm hoping that someone here can write up a how-to-guide on setting up AMD driver on linux.
pututu
)
Good luck with that! I too would be happy and surprised if someone would actually do that.
There are those that do run AMD GPUs with AMD drivers, but they haven't let on to what their secret is in getting them to work.
Proud member of the Old Farts Association
Installing ROCm drivers is
)
Installing ROCm drivers is fairly straight forward. but you have to be careful with what kernel you're running, and what card you have and what version of ROCm supports your GPU. i think they dropped Vega support from the new versions so you have to use an older one.
_________________________________________________________________________
Ian&Steve C.
)
I knew there was some quirky thing about getting AMD GPUs to run right with their drivers, but I didn't know what the issues were until now. I still don't know if there are any other issues, too.
Thanks Ian!
Proud member of the Old Farts Association
there was also an issue with
)
there was also an issue with BOINC GPU detection on some setups. i don't know if that was resolved at the driver or BOINC version
_________________________________________________________________________
GWGeorge007 wrote: pututu
)
I saved this from awhile back:
https://linuxconfig.org/amd-radeon-ubuntu-20-04-driver-installation
mikey wrote: I saved this
)
Good info! Thanks Mikey!
Proud member of the Old Farts Association
GWGeorge007 wrote: mikey
)
no problem