When i shut down the game for the night, I had this nice graph from my desktop gadget... The buzz at the end is from dieing, which apparently doesn't make you as cpu limited as usual, and then quitting the game. The funny thing is that the game tells me I am cpu limited... I don't see it D:
Game lies. I test settings using msi afterburner. Sometime gamу show me [GPU], but afterburner show only 17% gpu usage. I play few hours monitoring gpu and it never load above 90% Btw i got 90% in empty location. When i get in battle and my fps drop to 8 gpu show only 30% I think game limited by ping, not cpu or gpu. But this is just my theory.
I am pretty sure it is limited by the way it is coded, and not by the hardware. I could understand and to some degree accept it if I was at 100% on one core, but at the most I see one core go up to about 90% in the most intense battles... that is just wrong
I got E8600 cpu. 2 my friends got Core i7 930 and 2600K In some battles we got same fps. So i think there something else limit the game.
Exactly, this is just stupid, I have an E4700, it is realllllyyyy crappy. But still not using as much as it should be..
I know more about this than I really want and less than I really need to speak about it (lol), but I think it's more than simply an issue of the capacity of the GPU or CPU that is being measured by these tools. Generally speaking, there is at point at which no further capacity can be utilized due to waiting for procedure call interrupts to resolve, etc. An assembly line can only flow as fast as the slowest process involved, and there are always things that can be improved and bottlenecks that can't be economically eliminated. You can ask Joe Blow to trim parts a little faster, but you're not going to be willing to replace a $100,000 injection molding machine for a 1% increase in overall speed. Computers are somewhat analogous: the CPU is like a foreman both directing and working inside a complicated assembly process, and your foreman, in addition to its already hefty responsibilities, is currently experiencing heated arguments and a lack of perfect coordination with the server's foreman, LOL. It's more important for PS2 to be efficient and synchronized, rather than resource-consuming.
But even if it has to wait for the previous calculation to end before it can start a new one, shouldn't it at least max out one core?
115 FPS GPU 1 usage - 81% <- SLI config GPU 2 usage - 86% <- SLI config GPU 3 usage - 22% <-- Dedicated PhysX card. CPU usage - 41.4%
Out of curiosity, I can see the 115 FPS, but always in WG, is that typical, and what do you get in battle? Also, are you GPU or CPU limited?
Frankly, I don't know, but the game formerly used one core very heavily, and many people complained about it not (allegedly) being multithreaded. Now it seems to use two cores a little more evenly, at least on some people's systems. Furthermore, no monitoring tool (at least that a layman would use) provides a completely granular picture of what is actually happening from moment to moment, because if it polled that frequently, it would dramatically reduce the overall system performance by itself. Speaking very generally, most programs do not have consistently near 100% CPU utilization unless they are benchmarks or performing a single large, uniform task, like encoding a video file. Many of the latter type of programs allow you to restrict the CPU utilization so that you can still complete other tasks at the same time (like browsing the web, etc.). PS2 will always have to allow some headroom for the dynamic gameplay, modules like Vivox (the in-game voice chat), third party programs like fraps, TeamSpeak, Steam and all the other doodads you have running in the system tray. Finally, and I don't know everything there is to know about this by any means, but the CPU isn't simply waiting for its own calculations to finish. It can be waiting on a return from the video card, a texture file loading into memory from the hard drive, packets from the server, etc. Add in all the various system configurations and different capacity internet connections (as well as varying performance on those), server loading, the code that integrates a cluster of servers and gives us the appearance of playing on a single server ... I don't understand it all, but it's very clearly an enormously complex juggling act. That said, however, I get just as irritated as everyone else if I can't take advantage of double-xp weekend. I'm still a consumer and just want things to work.
Two great posts by a guy who understands the limitations of what we are dealing with here. Hopefully we will continue to see steady progress towards the majority of users being able to run the game smoothly. Only time will tell. Caffeine infused bananas for the code monkeys are in order.
Sobieski14: What tool are you using to monitor multiple GPUs in game? Looks neat, I'd like to try it to optimise my settings too.
MSI Afterburner : To monitor the GPUs HWiNFO64 : To monitor the CPU This is the most effective way to monitor the system. * People try to monitor the game not being full-screen and in being in windowed mode, it drastically changes results.