You do have Hyperthreading available to you. I don't think you need to do anything about it, just use them.
he has intentionally disabled SMT. which is a choice he's made for whatever reason. either for speed in whatever use-case, or for security threat mitigation.
he has intentionally disabled SMT. which is a choice he's made for whatever reason. either for speed in whatever use-case, or for security threat mitigation.
Okay, I was unaware of SMT being able to disable hyperthreading. But... how did you know that? I wasn't able to see his BIOS, assuming that is where it is disabled.
he has intentionally disabled SMT. which is a choice he's made for whatever reason. either for speed in whatever use-case, or for security threat mitigation.
Okay, I was unaware of SMT being able to disable hyperthreading. But... how did you know that? I wasn't able to see his BIOS, assuming that is where it is disabled.
SMT = Hyperthreading. it's the same thing. AMD calls it "SMT", Intel calls it "Hyperthreading" and is their trademark. It's just marketing.
I could tell because BOINC is reporting his host as having "64 processors". if SMT was enabled it would say "128 processors". I made the assumption that he hadn't messed with any BOINC settings to affect that reported value, and it seemed most likely that he had turned off SMT.
Has anybody started to use multiple All-Sky Gravitational Wave search on O3 v1.07 () windows_x86_64 in order to use GPU 100%?
As these "analysis & saves" around 50% & 100% take quite some time to do it with only CPU time! As it take ~20min for crunching on GPU & ~15min for CPU analysis.
What am I talking about? This, 12min gap of only using CPU:
& how does your app_config.xml looks like that multiple app crunching? ????
You need to try to stagger the task startups on the gpu so that they all don't converge at the 49% and 99% cpu offload points when running gpu task multiples.
Just suspend a task that starts anew on the gpu until the previous one had made progress halfway to one of its cpu compute intervals, then un-suspend the task.
You need to try to stagger the task startups on the gpu so that they all don't converge at the 49% and 99% cpu offload points when running gpu task multiples.
Just suspend a task that starts anew on the gpu until the previous one had made progress halfway to one of its cpu compute intervals, then un-suspend the task.
Have only WCG for
)
Have only WCG for CPU's.
Overloading is not seen so far. Yes, the hardware must be carefully balanced.
Two O3AS (one for each GPU) have the same performance as those four with .5 GPU.
Never thought, it would be the same performance.
More GPU-use is not running and not planned.
maeax wrote: Gary, have no
)
You do have Hyperthreading available to you. I don't think you need to do anything about it, just use them.
Proud member of the Old Farts Association
GWGeorge007 wrote: maeax
)
he has intentionally disabled SMT. which is a choice he's made for whatever reason. either for speed in whatever use-case, or for security threat mitigation.
_________________________________________________________________________
Sorry for the
)
Sorry for the misunderstanding.
HT is for me disabled. Of course, this CPU can do it.
The more Performance of HT is about 30%.
Ian&Steve C. wrote: he has
)
Okay, I was unaware of SMT being able to disable hyperthreading. But... how did you know that? I wasn't able to see his BIOS, assuming that is where it is disabled.
Proud member of the Old Farts Association
GWGeorge007 wrote:Ian&Steve
)
SMT = Hyperthreading. it's the same thing. AMD calls it "SMT", Intel calls it "Hyperthreading" and is their trademark. It's just marketing.
I could tell because BOINC is reporting his host as having "64 processors". if SMT was enabled it would say "128 processors". I made the assumption that he hadn't messed with any BOINC settings to affect that reported value, and it seemed most likely that he had turned off SMT.
_________________________________________________________________________
Thanks Ian! Makes sense.
)
Thanks Ian! Makes sense.
Proud member of the Old Farts Association
Has anybody started to use
)
Has anybody started to use multiple All-Sky Gravitational Wave search on O3 v1.07 () windows_x86_64 in order to use GPU 100%?
As these "analysis & saves" around 50% & 100% take quite some time to do it with only CPU time! As it take ~20min for crunching on GPU & ~15min for CPU analysis.
What am I talking about? This, 12min gap of only using CPU:
& how does your app_config.xml looks like that multiple app crunching? ????
non-profit org. Play4Life in Zagreb, Croatia, EU
You need to try to stagger
)
You need to try to stagger the task startups on the gpu so that they all don't converge at the 49% and 99% cpu offload points when running gpu task multiples.
Just suspend a task that starts anew on the gpu until the previous one had made progress halfway to one of its cpu compute intervals, then un-suspend the task.
Keith Myers wrote: You need
)
Thank you.
Immediate result can be seen:
non-profit org. Play4Life in Zagreb, Croatia, EU