Extremely poor DB reader performance on query

[rfairburn]

Fleet version: v4.56.0
Web browser and operating system:

---

💥  Actual behavior

A DB scaled to 2x the size of the recommeded architecture went to 99.9% usage with the following query accounting for essentially all of it:

SELECT CASE ( CASE WHEN EXISTS ( SELECT 1 FROM host_mdm_apple_profiles hmap WHERE h.uuid = hmap.host_uuid AND hmap.status = 'failed' AND NOT EXISTS ( SELECT 1 FROM host_mdm_apple_profiles hmap WHERE FALSE )) THEN 'profiles_failed' WHEN EXISTS ( SELECT 1 FROM host_mdm_apple_profiles hmap

🧑‍💻  Steps to reproduce

Unknown cause. Looks like mdm-related given the query.

🕯️ More info (optional)

N/A

[lukeheath]

Downgrading to P1 as the initial issue as been temporarily resolved.

[zayhanlon]

hey @gillespi314 any updates that we can share with the customer on where we are with this? thanks!

[gillespi314]

@zayhanlon, there is a PR under review currently. I'm hoping that we'll get that merged tomorrow and can start load testing.

[fleet-release]

Query strains, performance wanes,
Fleet whispers in code refrains,
Efficiency regains.