Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getDefaultThreadCount faulty #2

Open
ThomasTheGerman opened this issue Dec 12, 2020 · 3 comments
Open

getDefaultThreadCount faulty #2

ThomasTheGerman opened this issue Dec 12, 2020 · 3 comments

Comments

@ThomasTheGerman
Copy link

DWORD getDefaultThreadCount() {

As mentioned in this reddit thread, the logic in this function doesn't make any sense. For modern AMD Ryzen CPUs, it should return the logical value as well, just like on modern Intel CPUs.

@pagefault
Copy link

@tannisroot
Copy link

Even the article you linked states that

the vast majority of multithreaded games and applications work and scale really well when managing an active thread pool up to the number of logical cores that the processor supports

So it makes no sense for it to default to behavior that is only going to be beneficial for "a small number of games".
Also, evidenced by Cyberpunk, it's clear game developers do not and are not going to profile this and will release a product that is going to run poorly on modern AMD cpus for no reason.

@ThomasTheGerman
Copy link
Author

Default behavior should be to utilize the processor fully, SMT can be disabled in cases where performance regressions occur, which are rare.

SMT Regressions in rare edge cases aren't unique to AMD either, so the function as it is right now makes no sense in multiple ways.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants