Exactly. Yesterday I had to solve similar problem with nostr.build shitty MySQL DB. We had one query that too 3 seconds to execute on a short hardware. After looking deeply into it and removing, adding a few indexes and changing the query, I got the same result in 200ms and with much less response consumption πΆπΎπ«‘