Changes to let the performance tests hit the HTTP 429 code (too many requests) a little less.
1) Change core test logic to not clear disk cache on every run. Let individual tests configure this
2) After a performance test ran, we would let the editor scene load the same scene as a nicety (SetSuspendUpdate(false)). This is essentially a throw away scene load if you don't care about it. Don't do this either.
3) For Google Performance tests, let most tests just do a single pass (cold cache).
Also adds more profiling events during Unreal model loading (Cesium::LoadPrimitive event). This event was recently discovered as a bottleneck for certain performance tests (warm cache).
Changes to let the performance tests hit the HTTP 429 code (too many requests) a little less.
1) Change core test logic to not clear disk cache on every run. Let individual tests configure this 2) After a performance test ran, we would let the editor scene load the same scene as a nicety (
SetSuspendUpdate(false)
). This is essentially a throw away scene load if you don't care about it. Don't do this either. 3) For Google Performance tests, let most tests just do a single pass (cold cache).Also adds more profiling events during Unreal model loading (Cesium::LoadPrimitive event). This event was recently discovered as a bottleneck for certain performance tests (warm cache).
Before (Unreal Insights capture)![Profile before](https://github.com/CesiumGS/cesium-unreal/assets/130494071/e1736a4f-87f4-476b-ac30-42cd1b61cffc)
After![Profile after](https://github.com/CesiumGS/cesium-unreal/assets/130494071/29aab275-69a9-4fc9-b411-72b0f156b538)