Printable View
AMD can't give you 24 cores on socket TR4 - at least not in this generation. The infrastructure and silicon isn't there to support it.Quote:
Originally Posted by lumireleon
OTOH, they can already give you 32 cores (64 threads) in a single socket for around the same price. Motherboard support is still sadly hard to find, but the processors are there and ready to roll....
Quote:
Originally Posted by scaryjim
I almost started rubbing my nipples. God damn that's a beefy bugger
price vs performance is still a huge issue... maybe they just have an extreme horrible yield at Intel or trying to milk the world or whatever....
Would rather buy 2 16 core Ryzen CPUs and build 2 systems at current point unfortunately, besides with everything else in the systems adding up you would barely feel a difference anyway.
For streaming any CPU that isn't a bottleneck at 60fps is fine, because what streaming sites can send higher than 60fps content to viewers?
I'd be interested in how the 7401P compares, and I could see it getting a lot of the business customers that wanted cheaper xeons - system cost shouldn't be too far off this i9 (£600 cheaper CPU, but can't exploit the "cheap" X299 platform), and it does wide&slow better
Yeah, I'm surprised at just how much cheaper the P variants (single socket systems only) are compared to the normal ones: the 2P capable version of the same processor will set you back more than half as much again. Given that the 2P systems basically just grab half the PCIe lanes for infinity fabric, I'd be surprised if there's that much difference between them...Quote:
Originally Posted by Tunnah
I'm actually even more interested in the 7281 - a 16 core EPYC for less than £700. You get the full platform benefits - 8-cxhannel memory, 128 PCIe lanes, etc. but in a mainstream workstation price bracket.Quote:
Originally Posted by Xlucine
And let's remember that's a 2P capable chip, so you can slap two of those in a supporting motherboard for 32-core goodness at around £1300 of CPU cost.... :O_o1:
EDIT2: turns out ballicom are listing a dual socket SP3 motherboard for £650. So for the cost of *just* the i9 7980XE, you can buy two 16-core EPYC processors and a supporting motherboard....
"First off, the chip keeps to a 3.4GHz frequency under load. Second, HandBrake doesn't scale that well past 10 cores; we know this by looking at how the CPU behaves in Task Manager."
This is true both for Intel and AMD platforms. I sense some partial behaviour here...
How? They said pretty much the same thing on the threadripper review also...Quote:
Originally Posted by Sunderas
The issue isn't the gaming framerate but the encoding framerate. Last time I did any semi-professional encoding a 4C8T 4Ghz i7 managed around 3fps at high quality and 0.7fps at max quality without GPU acceleration. Things have moved on a lot since then but doubling IPC and quadrupling the core count would still only yield 24fps. There's plenty of space yet for more cores and scaling for encoding workloads. Not everyone's satisfied with the high-speed fixed function encoders in modern GPUs.Quote:
Originally Posted by Xlucine
So the programs that are slow all basically draw a frame at a time instead of part of one. That is always going to be a function of how fast you can encode and decode.
The ones that faster on multi cores that are slower use binary space partitioning or rendering buckets to divide the screen up into smaller pieces. To be blunt the ones using bsp partitioning would actually get better numbers with a faster video card at a higher resolution. AMD proved that years ago.
The way that works is smallest part of the screen that can be drawn without effecting what the piece next to it is calculated on the first thread, the even partition touching is skipped the next one not adjacent is started on a new thread. I tend to force 1/4 or 1/8th bsp or rendering buckets in engines that support it to get better quality than the mkg expect to support because if your bsp over heat the memory by saturating the bandwidth non ecc memory has not way to check to see if their are errors due to over heating. The point is the chip is getting the results that is expected by tech artists and getting better results in games is easy but might not be worth voiding your warranty on the video cards.
You can also force what is called fractal divisors in the hero engine based games to treat the screen as narrow blocks that go from top to the bottom to get ahead of screen tearing by using an odd numbered bsp forcing the engine to use narrow rectangles instead of square blocks.
The down side you can melt the memory on most video cards doing that. The card simply passes what it thinks is a complete screen frame to the card memory and swaps it out the monitor at a rate of about eight to one for what it would normally take to render the whole screen by using multiples of four cores and unused gpu shader cores. Basically it is sorta an exploit of the sli code but it does not require drivers only forcing the software to use bsp or rendering buckets instead of whole frames. In theory if the memory was not shared you could link a both a thread ripper and 18 core to cards and have them use the sli code to render to bsp in any game that is built into most gaming engines, to increase the quality you see on the screen until the memory on the video cards melt.
As scaryjim pointed out, there's no contest for bang-for-buck in parallel workloads between AMD and intel - an epyc system can throw far more cores at the problem than the i9, and much of the epyc product stack is cheaper. The only benefit to the intel CPU is a ~10% boost to framerate in some CPU-limited games, and you only hit that bottleneck when the game framerate is well in excess of what streaming games needs. For the same price as this system you could have a 17/1800 ryzen to play the games, and a dedicated capture box with an epyc CPU to encode the output. Many streamers use a separate computer to record, to save the load on the gaming system, so turning the recording computer into the recording&encoding system wouldn't change much.Quote:
Originally Posted by qasdfdsaq