Performance, SEO and Web Security

Database Performance Optimization

When an application slows down, the database is one of the first places to look. In MySQL, MariaDB and PostgreSQL we read slow query logs and query plans, and remove the bottleneck through index design, query rewriting, InnoDB and PostgreSQL memory settings, connection management and data clean-up.

EXPLAIN / ANALYZE

MariaDBMySQLPostgreSQLSlow query logIndex designInnoDB buffer poolConnection pooling

Service definition

What is database performance optimization, and who is it for?

First we measure: which queries determine the response time? Then we use the query plan to see why they’re slow, and fix them through indexes, query structure, the data model or server settings. A picture we often see in the field: RAM and CPU were added to the server, and the problem stayed put. In most cases, fixing a few missing or wrong indexes has a bigger effect than hardware.

01

Is a hardware upgrade necessary?

Usually, query and index fixes are enough first. If resources really aren’t sufficient after measurement, we make a capacity recommendation.

02

Is working on a live database risky?

Analysis is done with read-only access. Changes are applied in a maintenance window after a backup is taken.

03

Should we move to PostgreSQL?

It depends on the application and the team’s skills. Changing engines isn’t a cure for every slowdown; a cost-benefit analysis makes the decision.

Project stages

How do we proceed?

01 / STAGE

Measurement

Workload and queries.

02 / STAGE

Analysis

Plans and causes.

03 / STAGE

Remediation

Test and production.

04 / STAGE

Verification

Measurement and reporting.

Corporate Web

Let’s find and fix the queries slowing down your application

We discuss your database type, size and symptoms of slowness, and propose a measurement-based analysis and improvement plan.