Sorry to go off topic here a lil' bit just felt I should respond to this.


Quote Originally Posted by Valence View Post
I actually did more tests out of curiosity myself. It's not even the CPU bottlenecking anything......

It is most likely a CPU bottleneck in the engine somewhere. GPU/CPU usage/utilization doesn't tell the whole story.

In the charts below you'll see lots of data. What you should focus on is the GPU/CPU Busy/Frame Time Graph, and The GPU/CPU Wait time graphs.
- GPU and CPU BUSY time both measure how much time each resource is currently taking to render the current frame.
- GPU and CPU WAIT time measure how much time each resource is idling during the current frame, waiting on instructions.
- Frame Time is the measurement for how long it takes to render a frame

The First image is taken from me sitting outside my house. As you can see GPU busy pretty much matches the Frame-time, while CPU BUSY is slightly faster than each frame. This implies a Slight GPU Bottleneck. Higher frame rates tend to start running into a CPU bottleneck.



The Second Image is taken from Limsa Lominsa Plaza, with lots of players around. As you can see CPU Busy takes over twice as long as the previous scenario and Frame times are almost fairly close behind. GPU Busy shows that the GPU is taking significantly less time to do its rendering work on the current frame than the CPU. When you look at CPU/GPU wait you can see that the GPU is idling for a significant portion of the Frame Time waiting for instructions. My CPU utilization remains fairly close to what it was while sitting outside my house. This implies a Heavy CPU or Other System Bottleneck .



I can only speculate as to why this happens as I don't have access to the proper tools to analyze the engine at a deeper level. I'm going to guess that some of it has to do with just how old the engine is and that older versions of a lot of gaming/rendering APIs were not good about handling a lot of data being passed between the CPU,GPU, Storage and the Network. They would have to rework the client back-end to alleviate this at this point.

ANYWAYS...back to the topic at hand. Sorry to have interrupted the flow of the low/poly body convo.