Feed
Pro
Search

Author

Write
Drafts

Bug0 - The AI-native e2e QA regression testing Bug0 Browsers - Cloud Chromium on demand, per-minute, live preview Passmark - The open-source AI framework for regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap
Sign in

Search Hashnode

Search posts, tags, users, and pages

FeedDiscussion

Sharafath Ali

Code, Coffee, and Creativity – Full-Stack Developer on a Mission!

Jun 13

My PostgreSQL query went from 57ms to 1.4ms on a 1 million + row table. I didn't change the query. Here's what I did.

I was debugging a slow query on a users table with 1 million rows. EXPLAIN ANALYZE showed 57ms. I ran one SQL statement — didn't touch the query, didn't change the schema logic — and it dropped to 1.4

sharafath.hashnode.dev10 min read

#indexing #sql #postgresql #query-optimization #backend #api #api-basics #apis #api-gateway #nodejs #reactjs #frontend-development #frontend #mern #full-stack #databases #database

Responses(4)

databas

5d ago

did u check if the planner just cached the plan after an analyze run. its wierd how often that happens untill u realize the statistics were just stale and needed a quick refresh.

nice point. I actually ran "ANALYZE users;" and executed the query multiple times before taking the before/after samples. Initially the timings were a bit higher and varied, but after refreshing statistics and running the query a few times, they stabilized around the numbers I used. The earlier variance may have been due to stale PostgreSQL statistics and cache warming effects.

Sharafath Ali

Code, Coffee, and Creativity – Full-Stack Developer on a Mission!

5d ago

GameNetic

Jun 14

It's an informative article. Thanks for posting it man

Sharafath Ali

Code, Coffee, and Creativity – Full-Stack Developer on a Mission!

Jun 14

❤️❤️