July 31, 2026 at 12:00 am
Comments posted to this topic are about the item Fixing P1 Queries
July 31, 2026 at 9:18 am
The concept of prin is new to me, thanks for mentioning it
July 31, 2026 at 10:00 am
The thing with a P01 query is that there isn't much there to tune.
I worked on a system where the DB was under stress from 10s of thousands of calls to a P01. What we discovered was akin to the old ORM misconfiguration that retrieves a list of records then gets the child records row by row. The fix was to fix the app, not the DB.I
I see a repeat of the microservice design mistake where the service provided should have been more cohesive. Things that never should have been decoupled to the extent that they had been. It was akin to amputating limbs to lose weight.
The result was a lot of infrastructure and a massive amount of network traffic.
I've read some articles that are seeing the same thing happen with agentic AI. If the scope of what an agent can do is too small then whatever uses the agent has to find other agents to fill the gaps. It all burns tokens and consumes network bandwidth.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply