[DMS-818] Relational flattening performance spike #713
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bradbanister
force-pushed
the
DMS-818
branch
from
b90a1aa to
ee64a1b
Compare
bradbanister
changed the title
simpat-adam
approved these changes
Sep 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I took the existing joins-based query, which was 20% slower than original on my machine, and gave it to Claude Code after plugging in this PostgreSQL MCP. He turned it into something 2.5x faster than original.
So, I gave him the existing views-based query, which was 12% slower for me, and he made something 2.9x faster than original.
I would describe the level of effort for both of these optimizations to be very low. I was mostly eating pizza and typing with one hand, and know nothing about query optimization. Obviously, this piggybacked on the original effort of @simpat-adam