What is included

We work from measurements. Until it is clear what the limit actually is, any spending is a lottery.

Discuss the scope

Measurement under load

Processor, memory, disk queues and network, during working hours rather than in the quiet.

Server diagnostics

What is limiting things: resources, settings, background jobs, antivirus with no exclusions.

Database optimisation

Indexes, scheduled jobs and locks under concurrent use.

Network check

Port errors, duplex mismatches and link utilisation between nodes.

Configuration instead of purchase

Most findings are resolved by configuration rather than by money.

Measurement afterwards

Repeat measurements so the effect is proven rather than claimed.

How the work runs

Diagnostics take three to five days. Fixing depends on the findings, but it is often a matter of hours.

01

Collecting complaints

What exactly is slow, for whom and when. Specifics matter more than a general everything is slow.

02

Measurement

Observation during peak hours with the metrics recorded.

03

Remediation

We start with what is free: settings, exclusions and job schedules.

04

Verification

Repeat measurements compared against the originals.

Antivirus without exclusions on a database server is a finding we come across constantly. Real-time scanning of database files slows work down several times over. Setting the exclusions the vendor recommends takes half an hour and removes a problem people have complained about for months.

Frequently asked questions

Sometimes that is the right answer, but it has to be established by measurement. If the system is limited by its disks, a new processor changes nothing. Diagnostics cost incomparably less than a server and often show the purchase is unnecessary.

In our experience, a typical situation yields a 30 to 50 percent speed-up through configuration alone. More when a blunt error turns up, such as a missing index or a scheduled job running during working hours.

By figures rather than feelings. We record the metrics before the work and repeat the measurements afterwards, showing the difference. Impressions are subjective and depend on the user mood.

We will find what is slowing you down

Tell us what exactly is slow and for whom. We will measure it and show the real cause.