#ushell-cherrypick of 32395474 by dan.engelbrecht
#rb Devin.Doucette
#jira UE-210439
[FYI] tim.doerries, Zousar.Shaker, Stefan.Boberg
[CL 32452554 by dan engelbrecht in ue5-main branch]
[FYI] Devin.Doucette
Original CL Desc
-----------------------------------------------------------------
DDC: Eliminated most blocking during get requests in HttpCacheStore
#rb Zousar.Shaker
[CL 32422670 by keaton stewart in ue5-main branch]
[FYI] Zousar.Shaker
Original CL Desc
-----------------------------------------------------------------
Allow printing of "Any" content type responses.
[FYI] joakim.lindqvist
[CL 31546267 by zousar shaker in ue5-main branch]
The total is already served up as an Asset Type so had to and some logic to separate it in the view.
Changed sorting from Size to Count. I felt that sorting by highest count is more useful as is it clearly indicates the less efficient DDC work.
Added Hit Efficiency to Asset Stats and added this as an extra column to the UI
#rb Devin.Doucette
[CL 31009963 by mark lintott in ue5-main branch]
- Remove repeated log related to fetching cache stats
- Ensure that the Zen cache usage has log lines explaining the status of the caches it attempts to connect to (success or failure)
#rb Matt.Peters
[CL 30710842 by zousar shaker in ue5-main branch]
It's about 1/4 of CoreMinimal.h but rarely needed (Compression.h pulls on CriticalSection.h and Map.h that are costly).
#rb Yoan.StAmant
[CL 30683417 by aris theophanidis in ue5-main branch]
Instead of relying on a one-time blocking check with no reponse timeout, we now issue a blocking request with a 5 second idle time limit. If it fails, the store will still be created, but it will go into the same asyncronous re-evaluation loop as when performance is below the acceptable threshold and re-evaluate at 30 second intervals until both:
- Health is Ok
- Performance criteria (if any has been configured and is in use) is met
At which point it is activated. Health checks have been changed from the health/status endpoint to health/ready because we don't want to act if the server is running but not ready for requests (eg: during the time when it may be wiping data during a schema change.
The overall goal is that we don't force the entire session to execute without zenserver if zenserver was not ready at startup.
#rb Devin.Doucette
[CL 30295095 by zousar shaker in ue5-main branch]
