Steam installieren
Anmelden
|
Sprache
简体中文 (Vereinfachtes Chinesisch)
繁體中文 (Traditionelles Chinesisch)
日本語 (Japanisch)
한국어 (Koreanisch)
ไทย (Thai)
Български (Bulgarisch)
Čeština (Tschechisch)
Dansk (Dänisch)
English (Englisch)
Español – España (Spanisch – Spanien)
Español – Latinoamérica (Lateinamerikanisches Spanisch)
Ελληνικά (Griechisch)
Français (Französisch)
Italiano (Italienisch)
Bahasa Indonesia (Indonesisch)
Magyar (Ungarisch)
Nederlands (Niederländisch)
Norsk (Norwegisch)
Polski (Polnisch)
Português – Portugal (Portugiesisch – Portugal)
Português – Brasil (Portugiesisch – Brasilien)
Română (Rumänisch)
Русский (Russisch)
Suomi (Finnisch)
Svenska (Schwedisch)
Türkçe (Türkisch)
Tiếng Việt (Vietnamesisch)
Українська (Ukrainisch)
Ein Übersetzungsproblem melden
If you don't know how to tweak the advanced graphics settings, it won't matter what kind of hardware you use.
I’m not sure I would bother with the 3D variant of the 7950X. In fact I would hang back and see if the 9950X3D has 3D cache on both chiplets.
I’m not sold on the 3D cache variant in the long term. Maybe if both chiplets had the 3D cache I would be more excited. For now I’m sticking to my 5950X. It’s holding out at 167,000 people in my city. Interestingly enough the i9-10900K is holding out just as well but it’s using everything it has to keep up. Considering it is a older design it’s impressive
Part of it's my cooling solution is keeping me below the throttle point, another part of it is that this is exactly the kind of game that 3d v-cache would excel at. Much easier to handle the excessive API calls when most of the memory it's referencing most frequently will sit on the chip cache.
Hmm... That's a really interesting question.
I don't know for sure and wouldn't feel comfortable answering definitively without a benchmark. Typically the 3d v-cache is superior, even with more cores in a workload like this. Where you really see the advantage for more cores is productivity software.
Think about it like this:
Whenever the processor is running code, it identifies via algorithm which code is more likely called. That stays in the v-cache if it fits. So for a workload where you have lots of the same processes running over and over again - which happens frequently in games - the v-cache is superior because it doesn't incur a request to memory or storage to request that repeat data. So in an ideal situation, you're probably getting performance gains that would be superior to doubling the core count because of the how fast the cache return is.
Any workload where you have high multi-threading capability and where you have unique memory for every operation (editing/processing a video, running a database of large data sets, etc) is likely to benefit more from more cores.
So my gut is that the v-cache would be superior, but at the same time more cores will help you with some of the multi-threading workloads (meaning less thread contention). Having said that I'm not sure how well it scales beyond 8 cores, and the answer to that would likely give us some more insight as to the answer.
But each time the CPU can stay in the CPU package, the better the performance and the more bang you get for each core. So theoretically I would say the v-cache might be better for this workload.
150k people that get 100% at 3x speed..... 70% at 2x speed....