L3 Cache Considerations (Figure 3)
The overall trend for MSFS2020 is that processor utilization is difficult to increase on any processor.
Especially when there is a lot of terrain and object loading, CPU clock and power consumption will increase, GPU load will not increase, GPU power consumption will drop, and FPS will worsen. In this case, storage and network are overloaded.
Glass cockpit and VFR maps use HTML/XML, which takes time to render (a feature that seems to have been included in SU10 for improvement). There is also a lot of string object and memory re-referencing, which runs and loads every instrument update frame.
In both cases, not much computation is performed, and memory accesses make up the majority.
Thus, the characteristics of MSFS are memory/storage/network IO-centric applications. There is a lot of computation, such as 3D geometry within the main thread, but there is more IO, so the ALU waits for IO, limiting the effective performance (FPS).
The CPU caches memory addresses, data contents, and code for referencing. If the cache is hit, memory accesses are not needed and IO latency is accelerated.
Although GPU power consumption is higher on the 5800X3D than on the 5950X, the overall FPS is better. (Figure 3)
The current L3 cache trend for high-end CPUs is 30-32 MB, which is (probably) not enough for the MSFS2020. Therefore, the 5800X3D with 96MB of L3 cache is expected to increase its speed. Our future may be bright, as it has been suggested that it may increase in future processors.
(Only 5800X3D-Narita 34L(W) was corrected to 500 because the axis was 400.)
5 Likes