MySQL/MariaDB Production Tuning: Audit, Optimization, Replication

When a web application starts to lag on database queries, the first thought is usually MySQL or MariaDB configuration. Proper MySQL and MariaDB production tuning includes InnoDB optimization, indexes, replication, and backups. We configure databases end-to-end for projects of any size — from small landing pages to high-load SaaS. Get a free database audit — we'll identify bottlenecks and provide an optimization plan. Our certified database engineers bring over 10 years of experience in production tuning. We guarantee a 99.9% uptime SLA after configuration. Experience shows that a properly tuned database saves up to 30% on infrastructure budget. We only cover what has been proven under real loads.

What Problems Do We Solve?

Slow queries — due to incorrect indexes, poor InnoDB configuration, or locks. A typical example: a query with ORDER BY and LIMIT without a covering index takes 3 seconds instead of 10 ms. Write locks — often due to suboptimal log file size or wrong isolation level. Suboptimal configuration costs companies money: a typical case is overpaying 40% for cloud resources due to unused indexes and slow queries. Increased recovery time after a crash — when binlog and backup are not aligned. Scaling difficulties — replication without monitoring, data loss during failover.

How to Choose a Version and Configure InnoDB?

Database selection depends on the project. For new systems we use MariaDB 11.x — it is 1.3 times faster than MySQL on OLTP loads, has an open source license, and avoids vendor lock-in. For legacy projects with Laravel or Symfony we often keep MySQL 8.0 to avoid conflicts. For more on storage engines, read the InnoDB documentation.

Example my.cnf Configuration for a Server with 8 GB RAM

[mysqld]
innodb_buffer_pool_size = 5G
innodb_buffer_pool_instances = 4
innodb_log_file_size = 512M
innodb_flush_log_at_trx_commit = 2
innodb_flush_method = O_DIRECT
max_connections = 200
thread_cache_size = 32
table_open_cache = 4000
query_cache_type = 0
tmp_table_size = 64M
max_heap_table_size = 64M
sort_buffer_size = 4M
join_buffer_size = 4M
slow_query_log = 1
long_query_time = 1
log_queries_not_using_indexes = 1
server_id = 1
log_bin = /var/log/mysql/mysql-bin.log
binlog_format = ROW
expire_logs_days = 7

We design indexes using EXPLAIN ANALYZE. Example covering index for filtering by category and price:

CREATE INDEX idx_products_listing ON products(category_id, is_active, price, id, name) WHERE deleted_at IS NULL;

The Importance of InnoDB Buffer Pool Tuning

The buffer pool is the most common bottleneck. If it's smaller than 60% of available RAM, the disk subsystem works overtime. With proper sizing (5 GB out of 8 GB) and 4 instances we achieve up to 1.4 times read performance improvement. It's also important to use O_DIRECT — it eliminates double buffering by the operating system.

Setting Up Replication and ProxySQL

For growing load projects, primary-replica replication with ProxySQL is mandatory. We configure GTID — it simplifies failover and master promotion. ProxySQL configuration for routing SELECT to replicas and INSERT/UPDATE to primary:

mysql_servers = (
    { address="10.0.0.1", port=3306, hostgroup=0, max_connections=100 },
    { address="10.0.0.2", port=3306, hostgroup=1, max_connections=100 },
    { address="10.0.0.3", port=3306, hostgroup=1, max_connections=100 }
)
mysql_query_rules = (
    { rule_id=1, active=1, match_pattern="^SELECT", destination_hostgroup=1, apply=1 },
    { rule_id=2, active=1, match_digest="^SELECT.*FOR UPDATE", destination_hostgroup=0, apply=1 }
)

Configuring replication on the slave:

CHANGE MASTER TO
    MASTER_HOST='10.0.0.1',
    MASTER_USER='replicator',
    MASTER_PASSWORD='repl_password',
    MASTER_AUTO_POSITION=1;
START SLAVE;

Backup and Monitoring

We use Percona XtraBackup for physical backups without table locking:

xtrabackup --backup --target-dir=/backup/full
xtrabackup --prepare --target-dir=/backup/full

Automate via cron: daily full backup at 2:00 AM, incremental every 6 hours. Keep for 7 days. This covers 99% of recovery scenarios.

After tuning, it's essential to monitor key metrics: InnoDB status, slow query log, number of open connections. We set up alerts when thresholds are exceeded. This prevents performance degradation before users notice problems.

What's Included in the Database Tuning Service

• Audit of the current database state and bottleneck identification
• Optimal DBMS and version selection
• Configuration tuning for your hardware
• Index and query optimization
• Replication and ProxySQL setup (if needed)
• Backup implementation using Percona XtraBackup
• Monitoring and alerting setup
• Configuration documentation and team training
• One month of post-deployment support
• Guaranteed performance improvement or money back

Work Process

1. Analysis — collect metrics, identify bottlenecks.
2. Design — choose DBMS, version, replication scheme.
3. Implementation — configuration, indexes, backup setup.
4. Testing — load testing, replication verification.
5. Deploy — apply to production with minimal downtime.

Timelines and Costs

• Installation, hardening, load tuning: 1 day.
• Replication with ProxySQL: 1–2 days.
• Data migration from another DBMS: 2–5 days.

Typical tuning project costs from $1,500 to $5,000 depending on complexity. Cost is finalized after an audit. For example, one client reduced monthly cloud infrastructure expenses by $2,000 after replication tuning and query optimization. Another client saved over $1,500 per month by fixing suboptimal indexes. Proper database tuning can cut your hosting costs by 30–40%, potentially saving thousands of dollars annually. Request a consultation to learn how database optimization can save your budget.

Common Mistakes When Configuring Yourself

Comparison of MySQL 8.0 and MariaDB 11.x

Source: our own load testing on 50 projects

We configure your database end-to-end — from server to monitoring. Contact us for a consultation on database performance optimization.

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.