- #Mpeg streamclip only uses around 30 percent of cpu 1080p#
- #Mpeg streamclip only uses around 30 percent of cpu driver#
- #Mpeg streamclip only uses around 30 percent of cpu Patch#
- #Mpeg streamclip only uses around 30 percent of cpu plus#
So for the newer CPU architectures it's less about core count and more about the IPC that particular architecture offers. But it does mean you're right on the edge with this part, and slower 6-core/12-thread processors will start to see a decline in performance, assuming your GPU is capable of driving over 100 fps using your desired quality settings. Despite this heavy utilization, the game didn't stutter, at least no more than what was witnessed using higher core count Zen 3 processors. The 5600X was similar despite being a 6-core/12-thread CPU as the game didn't max out the 5800X, meaning a fast 6-core Zen 3 processor is still fine, though it's right on the edge with utilization often locked at 100%. So the only reason the 5950X was a few frames faster would be due to the slight increase in frequency, as stuff like cache capacity is the same per CCD. With the 5800X, utilization was more in the range of 70-80%. In the case of Zen 3, the 8 cores aren't maxed out, so the 5590X saw utilization in 128 player games of around 30 to 40%. What's really interesting to note though is that despite the game being very CPU demanding - at least by normal gaming standards - the 5950X was just 5% faster than the 5600X when comparing the average frame rate, and up to 14% faster for the 1% low.īattlefield 2042 utilizes 8 cores when available, so with the 5950X half the cores essentially did nothing. The 12600K was also 9% faster than the 5800X, though the 1% low and 0.1% low data was comparable.
#Mpeg streamclip only uses around 30 percent of cpu 1080p#
Typically, we test CPU performance at lower resolutions such as 1080p to help remove any GPU bottlenecks, though with Battlefield 2042 multiplayer that's not really necessary as you'll see soon when we test at 1440p.īut here at 1080p, we see that for the best performance you'll want a 12th-gen Intel processor, though we're talking about an 8% performance advantage for the 12900K over the 5950X. All configurations used 32GB of dual-rank, dual-channel DDR4-3200 CL14 memory, and we've also included some memory results using a few different configurations for good measure.įor now, let's start with the CPU testing.
#Mpeg streamclip only uses around 30 percent of cpu driver#
The test was verified with GeForce Game Ready Driver 496.76 WHQL drivers, using the latest version of the game.
#Mpeg streamclip only uses around 30 percent of cpu Patch#
We believe the Nvidia driver mostly addressed DLSS-related issues, while the game patch mostly addressed stability and bug fixes. Neither of these updates affected the results. We used the GeForce RTX 3090 for testing as it was typically faster than the Radeon RX 6900 XT in this game, as we discovered in the GPU benchmark a week ago. It's also worth noting that during our testing, the game received a patch, and Nvidia released an updated GPU driver. But please be aware the margin for error is higher when compared to our more controlled testing, and I was certainly seeing a bigger run to run variance.
The 128-player conquest data is based on 3 minutes of gameplay and because the amount of players in the server can change, as well as what the players are actually doing, there's more variance, but the 3-run average helps to address this. But we're more confident in the accuracy of that data because it's a more controlled test.
#Mpeg streamclip only uses around 30 percent of cpu plus#
It isn't as CPU demanding as there are less players, plus the AI load is different. We've also included separate 60 second testing on the same map using bots which is a more controlled environment as I have a fixed number of players in the game and they're all active. This along with a number of other factors meant that I was only able to test 3 or 4 CPUs per day. It might not be an exact apples to apples comparison, but it's certainly ballpark.īut testing 20+ configurations for comparing a wide range of CPUs is a massive undertaking, and long story short it's taken me 7 straight days of doing nothing but trying to load into a 128-player conquest match on the same map (and succeeded!).įor testing we've used the Orbital map, and of course that map wasn't always available in the rotation, so we had to wait for it to cycle into use.
play the game on the same map under the same conditions for a few minutes, do that three times to record the average, and you have a pretty good idea of how they compare. Testing one or two hardware configurations isn't too difficult or that time consuming. The problem faced when trying to test a multiplayer game like Battlefield 2042 is that it's extremely difficult to get accurate comparative data. Today we're taking a look at CPU performance in Battlefield 2042 and this may well be the most difficult benchmark we've ever done.
0 kommentar(er)
