this post was submitted on 03 Jun 2023
149 points (100.0% liked)
Chat
7499 readers
5 users here now
Relaxed section for discussion and debate that doesn't fit anywhere else. Whether it's advice, how your week is going, a link that's at the back of your mind, or something like that, it can likely go here.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm no dev on the project myself, and I haven't studied that query enough to know, but yeah they are some monster queries. I'd have to fire up pgadmin and try them out on my personal instance to understand them better.
But as for your curiosity, I had an issue with a microservice at my job that is very sensitive to database latency (makes one call, roughly 600 requests per second on average, up to 1200 in spikes.) We solved an issue with some of the joins going on by making a materialised view for what we knew didn't change more than once per day, which we then scheduled with pg_cron to refresh concurrently (concurrently being key so we don't lock out reads.) Reduced our query times significantly - ie, down to milliseconds vs up to 20 seconds.
Really boils down to how often some data needs to change, so you can make some sort of way of caching it.