Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Yeah, highly so. You can expect all modern games be heavily multi-core dependant.
Odyssey does ALSO require strong single-threaded performance though. It needs both a lot cores and they need to be strong.
Yeah, 1.25v on core, cant get no lower, i also use a 360mm aio, temps range around 70s or so on aida, summer months it can be a bit higher.
Some people do need a wide range of voltage to get 4.5 or even over, i need 1.29 to get to 4.6 and temps hit around 80c, not comfortable with it 80s.
Yet most games are GPU > CPU intensive. So it's rare for your CPU to "Bottleneck" your GPU in games. With the hardware you cited I would expect your GPU to be the first to hold you back and it will hold you back because you are asking to much from the system.
To be an advance computer user you should learn to find and address bottlenecks. Start off by learning what graphic settings only impact GPU performance, what impacts CPU and what impacts them both. You might be surprised by the amount/type of graphic settings that have nothing to do with your CPU.
Next you want to learn how to read performance logs. This can help you find and best address bottlenecks.
Bottlenecks are something you can not eliminate, yet you can optimize around them. When programmers are looking to optimize their code, they look at what tasks are taking the longest to complete. Optimizing code that takes 1 millisecond to complete wont help if the cycle is still stuck with a bit of code that takes 10 milliseconds to complete. AKA the program is only as fast as it's weakest link.
Also remember the performance of a computer is not only a sum of all it's part but also what tasks we ask of the computer.