PostgreSQL Tuning: shared_buffers, work_mem, effective_cache_size

Default PostgreSQL configuration is tuned for modest hardware and is inefficient on modern servers. shared_buffers = 128MB, work_mem = 4MB — these settings leave 95% of memory unused. For example, a server with 32 GB RAM using default settings uses only 128 MB for cache — the database idles while queries lag. Proper tuning yields at least 30% performance gain and reduces disk subsystem load. We configure based on your profile: OLTP, analytics, or mixed. Our team has completed 50+ successful projects, with a guarantee of results.

PostgreSQL tuning is not just "set numbers higher" — it's understanding how the planner uses memory, how caching works, and how to avoid I/O bottlenecks. Adjusting shared_buffers, work_mem, and effective_cache_size is fundamental but critical. Incorrect configuration leads to swapping or RAM underutilization. Our engineers analyze your server and workload to find optimal values.

Problems We Solve

Insufficient work_mem for Analytics

Slow reports due to sorts spilling to disk. A typical query with ORDER BY on a large table takes minutes when the plan shows disk sort. This is fixed by increasing work_mem for specific queries or creating covering indexes.

Incorrect effective_cache_size

The planner chooses sequential scans over index scans because it thinks the cache is small. Setting effective_cache_size to 75% of RAM immediately increases index scan usage.

shared_buffers Conflict with OS Cache

Too large shared_buffers (above 25% RAM) competes with the operating system's cache, reducing cache hit ratio. Checking via pg_buffercache helps find the optimum.

How We Do It

We use a proven methodology: audit current configuration, analyze query plans, and tune parameters to the workload. Example: an e-commerce site with 10,000 queries per minute. After tuning, report execution time dropped from 5 minutes to 20 seconds, cache hit ratio rose from 97% to 99.8%.

Tool Stack

• PostgreSQL 14–17
• pgtune for initial estimation
• pg_buffercache for buffer monitoring
• EXPLAIN ANALYZE for query analysis
• pg_stat_statements for identifying heavy queries

Tuning Process

1. Audit current configuration and workload profile
2. Collect metrics: cache hit ratio, buffer usage, query plans
3. Set shared_buffers — 25% RAM for dedicated server
4. Set work_mem — 4–64 MB for OLTP, 256 MB–1 GB for analytics
5. Set effective_cache_size — 75% RAM
6. Optimize planner: random_page_cost for SSD, parallel query parameters
7. Configure checkpoint and WAL for disk type (SSD/HDD)
8. Monitor hit rate and pg_buffercache after changes
9. Document all changes
10. 30-day guarantee: if performance doesn't improve, we re-tune for free

Memory Parameter Tuning

How to Set shared_buffers for OLTP?

The database's global page cache for all processes. For a dedicated server — 25% RAM. On a 32 GB server, that is 8 GB. Above 25% may conflict with OS cache. Check if shared_buffers is sufficient via hit ratio: if cache_hit_ratio < 99%, either shared_buffers is small or the working set doesn't fit in memory. Use pg_buffercache to see which tables and indexes occupy the buffer. Increase shared_buffers to up to 25% RAM, but no more than 8 GB on Linux due to architectural limits.

What to Do When cache_hit_ratio Is Low?

If cache_hit_ratio is below 99%, tuning is needed. Check shared_buffers — may need increase. Also consider adding indexes. For analytical queries, increasing work_mem may help. Use the query from the code block to check hit rate.

Why a Small work_mem Is Often Better Than a Large One

work_mem is memory per sort/hash join operation within a query. If a query has 3 sort nodes, it can consume 3 × work_mem. At 100 concurrent connections with heavy queries, usage could be 100 × 3 × work_mem. Too high a value causes swapping. A common mistake: setting 64 MB globally, while 100 connections with 4 sorts each = 100 × 4 × 64 MB = 25.6 GB. Start with 16 MB, increase for specific queries via SET LOCAL. For OLTP workloads, high work_mem leads to memory overuse and performance degradation due to swapping. Our method: analyze query plans, identify sorts on disk, increase work_mem only for problematic queries.

effective_cache_size: A Simple Hint to the Planner

A hint to the planner about available OS cache + shared_buffers. For a 32 GB server: 24 GB. Influences the choice between index scan and seq scan. Does not reserve memory but is critical for correct plan selection. More details in the official PostgreSQL documentation. Recommended setting: 75% of RAM.

maintenance_work_mem: For Maintenance Operations

For VACUUM, CREATE INDEX, ALTER TABLE. Increase only during maintenance. A value of 2 GB suffices for most tasks. Do not keep it high permanently — it saves memory.

Tuning the Planner and Performance Monitoring

Cost Parameters and Parallel Queries

# Cost model for SSD
random_page_cost = 1.1    # SSD: 1.1, HDD: 4.0 (default)
seq_page_cost    = 1.0

# Parallel queries (PostgreSQL 9.6+)
max_parallel_workers_per_gather = 4
max_parallel_workers = 8
parallel_tuple_cost  = 0.1
parallel_setup_cost  = 1000.0

Monitoring Hit Rate and Buffer Cache

-- Cache hit ratio
SELECT
    sum(heap_blks_hit)  AS heap_hit,
    sum(heap_blks_read) AS heap_read,
    round(
        sum(heap_blks_hit)::numeric /
        nullif(sum(heap_blks_hit) + sum(heap_blks_read), 0) * 100, 2
    ) AS cache_hit_ratio
FROM pg_statio_user_tables;

-- Buffer usage details
CREATE EXTENSION IF NOT EXISTS pg_buffercache;
SELECT c.relname, count(*) AS buffers,
       round(count(*) * 8192.0 / 1024 / 1024, 1) AS size_mb
FROM pg_buffercache b
JOIN pg_class c ON b.relfilenode = c.relfilenode
GROUP BY c.relname
ORDER BY buffers DESC
LIMIT 20;

If cache_hit_ratio < 99% — tuning shared_buffers or adding an index is needed.

Tuning by Workload: OLTP, Analytics, Mixed

Checkpoint and WAL

checkpoint_completion_target = 0.9
checkpoint_timeout = 15min
max_wal_size = 4GB
fsync = on
synchronous_commit = on

Workload Profile Comparison

Practical Example: Sort Optimization

A query slowly executes ORDER BY on a large table — sort goes to disk via temporary file:

EXPLAIN (ANALYZE, BUFFERS, FORMAT TEXT)
SELECT * FROM events
WHERE user_id = 1
ORDER BY created_at DESC
LIMIT 100;

If output shows "Sort Method: external merge Disk: 45678kB" — need an index or more work_mem.

CREATE INDEX CONCURRENTLY idx_events_user_date
  ON events(user_id, created_at DESC)
  INCLUDE (id, event_type, payload);

Applying Changes

After changing parameters, run SELECT pg_reload_conf(); to apply.

Common PostgreSQL Tuning Mistakes

Conclusion

Proper PostgreSQL tuning yields significant performance gains and infrastructure savings. We guarantee at least 30% improvement or we re-tune for free within 30 days. Contact us for a consultation and order professional PostgreSQL tuning.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.