csciguy8

Another instance of a very slow build, 2 hr 6 min. (Windows50) https://github.com/CesiumGS/cesium-unreal/actions/runs/5969272697/job/16194821201

Thanks for all the investigation @kring > So... why in the world is the slower build reading over 10x as much data from EBS?! > All told, we're reading 52...

Another interesting example where the workflow seems to have gone to lunch (3 hours+) with two different test job instances, in two different places. https://github.com/CesiumGS/cesium-unreal/actions/runs/6225004383 

Did a quick search for MsMpEng, and it seems to plague more than just us. There are a variety of solutions for disabling this further, whether excluding its own directory...

> So I really have no idea what MsMpEng.exe is doing with all that CPU time. Maybe scanning newly generated files from the build? An easy tweak might be to...

Closing this. I haven't seen this behavior in a while. My guess is that the switch to GitHub hosted runners fixed it.

For reference, here's some of the latest related profiles in Unreal Insights...  from [this PR](https://github.com/CesiumGS/cesium-unreal/pull/1356). Setting up the mesh and material look to be around half the time spent...

> Waiting in a worker thread is much better than waiting in the game thread.... But it doesn't defeat the point, in any case. Ah, I think I see. So...

@j9liu Thanks! Just one caveat with this chain of PRs. I did find a bug, and fixed it, but snuck the fix to the[ last PR in this chain](https://github.com/CesiumGS/cesium-unreal/pull/1390). Here's...

Hey @azrogers , thanks for the review. I noticed that you made some misc formatting changes, and now I'm no longer able to open the dynamic pawn blueprint in UE...