Ryzen 5600x 6-core CPU - enable SMT to get 12 virtual CPUs or stay with the 6 ?

[jcommdcs]

I would like to get your feedback regarding the SMT option (AMD multithreading) for a Ryzen 5600x, 6 core CPU I am using.

My GPU is a Nvidia RTX 3060 Ti with "just" 8 GB.

Should I enable SMT to get the 12 virtual CPUs instead of the default 6, now that DCS is "natively" multithreaded ?

Thanks for any opinions / hints !

EDIT: Well, should have used the "Search" engine, I know...

 

Edited October 6, 2024 by jcommdcs

[twistking]

you should have it ON unless you get worse performance with it. if you're unsure, leave it ON.
it will generally improve your pc performance significantly and therefore should only be deactivated if you encounter persistent issues with programs you regularly use.

[Dr_Pavelheer]

Multithreading in software and hyperthreading are different things

[Hiob]

6 hours ago, jcommdcs said:

I would like to get your feedback regarding the SMT option (AMD multithreading) for a Ryzen 5600x, 6 core CPU I am using.

My GPU is a Nvidia RTX 3060 Ti with "just" 8 GB.

Should I enable SMT to get the 12 virtual CPUs instead of the default 6, now that DCS is "natively" multithreaded ?

Thanks for any opinions / hints !

EDIT: Well, should have used the "Search" engine, I know...

 

 

I‘d say try it. You can easily switch back and forth when booting. I agree that the baseline should be SMT on (unless you have more physical cores than you need).

If you encounter problems like frametime spikes, microstuttering etc…. try turning it off and see of it improves.

[jcommdcs]

8 minutes ago, Dr_Pavelheer said:

Multithreading in software and hyperthreading are different things

OFC..., my bad

 

Edited October 6, 2024 by jcommdcs

[Hoirtel]

I have been trying SMT on and off today with my 7800X3D. No major changes in performance but the terrain stutter at low level is definitely worse with it off. I was a bit surprised but it was very repeatable using the same track file.

Also even stranger was that with SMT off I could see a tiny bump every second on the frame counter green line (simulation). This wasn't really noticeable in game, but was very clear to see in the main menu. SMT back on and it was gone. It may have been there in the game but the line was rougher generally as the terrain stuttered more. 

[Dr_Pavelheer]

1 hour ago, jcommdcs said:

OFC..., my bad

 

 

That's what this forum is for

[MAXsenna]

That's what this forum is for

Exactly this! Wise words!

Sent from my SM-A536B using Tapatalk

[Aluminum Donkey]

On 10/6/2024 at 4:42 AM, jcommdcs said:

I would like to get your feedback regarding the SMT option (AMD multithreading) for a Ryzen 5600x, 6 core CPU I am using.

My GPU is a Nvidia RTX 3060 Ti with "just" 8 GB.

Should I enable SMT to get the 12 virtual CPUs instead of the default 6, now that DCS is "natively" multithreaded ?

Thanks for any opinions / hints !

EDIT: Well, should have used the "Search" engine, I know...

 

 

I have a 5800X (non-X3D) processor which has 8 cores and 16 threads. I find DCS performs much better with SMT enabled for all 16 threads, when I turn off SMT I get very heavy stuttering over Paris and London in the Normandy 2.0 map.

Enabling SMT allows DCS MT to run pretty decently, but when I fly low over Paris or London I still get noticeable frame pacing variations making it look like the plane is speeding up and slowing down. At least it doesn't stutter heavily like with SMT turned off.

Try it yourself and see! DCS is brutally demanding with all the eye candy cranked up so I think you're better off with SMT enabled. It generally makes everything run better including DCS.

AD

EDIT: I eliminated the stuttering and annoying frametime variations simply by turning off Civil Traffic! Runs like an absolute charm now. I haven't tried it with SMT turned off yet but see no need to.

Edited October 21, 2024 by Aluminum Donkey

[Hiob]

Unfortunately it seems that there is no "one fits all" solution, when it comes to such issues. There are so many variables at play that all need to work seemlessly together to have a really smooth experience.
There are some things that I have personally put in the "pretty sure it is bad for performance" drawer - but even those are sometimes opposed by others.
I would say it is reasonable to just build a toolbox of possible culprtis and solutions and then just apply it in the personal preferred order when necessary.

Hyperthreading/SMT on/off is just one of those tools. Not the most important (imho) but one of the easiest to test. Therefore it is pretty high up on my personal checklist.