MySQL Performance Tuning: InnoDB, Caches, and Query Optimization

MySQL Performance Tuning: InnoDB, Caches, and Query Optimization

Imagine: an e-commerce site handling 50,000 orders per day, MySQL with default configuration — innodb_buffer_pool_size = 128M, query_cache enabled, max_connections = 151. Result: crashes every 2 hours, p95 latency 450 ms. After tuning — 85 ms, 5.3 times faster. Our engineers with 10 years of experience and 500+ projects tune InnoDB, caches, and queries for your workload. p95 latency drops from 450 ms to 85 ms — 5.3x improvement. Proper buffer pool configuration boosts hit rate to 99.4%. In one project, write performance increased 3x after enlarging the redo log.

How to Tune InnoDB Buffer Pool?

InnoDB is MySQL's primary storage engine. Its buffer pool is the main cache for data and index pages. As per the MySQL Performance Tuning Guide, it should occupy 70–80% of RAM on a dedicated server. Example configuration for a server with 32 GB RAM:

[mysqld]
innodb_buffer_pool_size = 24G
innodb_buffer_pool_instances = 24
innodb_buffer_pool_dump_at_shutdown = ON
innodb_buffer_pool_load_at_startup  = ON
innodb_log_file_size = 1G
innodb_log_files_in_group = 2
innodb_log_buffer_size = 64M
innodb_flush_method = O_DIRECT
innodb_read_io_threads = 8
innodb_write_io_threads = 8
innodb_io_capacity = 2000
innodb_io_capacity_max = 4000
innodb_adaptive_flushing = ON
innodb_use_native_aio = ON
max_connections = 500
thread_cache_size = 50
thread_stack = 256K
wait_timeout = 300
open_files_limit = 65535
table_open_cache = 4000
table_definition_cache = 2000

Check effectiveness via hit rate:

SELECT (1 - (SELECT variable_value FROM information_schema.global_status WHERE variable_name = 'Innodb_buffer_pool_reads') / 
       (SELECT variable_value FROM information_schema.global_status WHERE variable_name = 'Innodb_buffer_pool_read_requests')) * 100 AS hit_rate_pct;

Target: hit rate >99%. If lower, increase buffer pool or optimize indexes. In a typical project, hit rate rises from 87% to 99.4%.

Why You Must Disable Query Cache?

query_cache in MySQL 5.7 and below uses a mutex on the entire cache on every write. On high-load sites, up to 40% of CPU time is spent on query_cache_mutex. In MySQL 8.0, it is removed. Application-level caching (Redis, Memcached) is the correct solution. Disable it in config:

query_cache_type = 0
query_cache_size = 0

How to Find and Optimize Slow Queries?

Enable slow query log and analyze with pt-query-digest. Typical issues: full table scans, missing indexes, sorting without indexes. Slow queries are those taking longer than 1 second.

slow_query_log = ON
slow_query_log_file = /var/log/mysql/slow.log
long_query_time = 1
log_queries_not_using_indexes = ON
min_examined_row_limit = 100

Analysis command:

pt-query-digest /var/log/mysql/slow.log --limit 20 --output report > /tmp/slow_report.txt

Use EXPLAIN FORMAT=JSON for analysis. Look for "access_type": "ALL" (full table scan) and "using_filesort": true. Create composite indexes, e.g.: ALTER TABLE orders ADD INDEX idx_status_date (status, created_at DESC);.

How to Tune Redo Log for Maximum Write Performance?

Increasing innodb_log_file_size (or innodb_redo_log_capacity in MySQL 8.0) reduces checkpoint frequency, boosting write throughput. On high-load sites, this lowers latency and increases transaction throughput. In one project, after increasing log file size from 256M to 1G, write performance increased 3x.

Before and After Tuning Comparison

Our Tuning Process

• Configuration audit: review my.cnf, buffer pool, redo log, buffers, I/O. Capture current metrics via Performance Schema.
• Slow log analysis: download logs for a week, run through pt-query-digest, select top 20 by time. For each, run EXPLAIN.
• Parameter tuning: adjust buffer pool, redo log, buffers, connections, I/O. Restart MySQL during maintenance window.
• Query optimization: create/refine indexes, rewrite heavy JOINs, add caching.
• Monitoring: deploy Performance Schema, set up alerts for slow queries and hit rate. Document with report.

What's Included

• Configuration audit: check mysql config, buffer pool, redo log, buffers, I/O.
• Slow log analysis: identify top 20 heavy queries, index recommendations.
• Performance tuning: parameter adjustments, index optimization, query restructuring.
• Monitoring: deploy Performance Schema, scripts for regular checks.
• Documentation: report with changes, rationale, and measurement results.
• Support: 2 weeks post-tuning for adjustments.

Cost Savings from Tuning

On average, clients save a significant amount per month after optimization. This not only reduces infrastructure costs but also improves application speed, directly impacting conversion rates. Our engineers will calculate the savings for your project individually.

To achieve similar results, contact us — we will tune your MySQL. Order optimization and we guarantee measurable results. Get a consultation: we will assess your project within 1-2 days.

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.