Performance Tuning
Performance tuning finds why an application became slow and fixes the cause. It starts with measurement on the screens your team reports, across the database, application code, network and external services.
Measure before changing anything
Recorded timings replace guesses. Time is measured on the screens your team reports as slow, split between the database, the application code, the network and any external service. The largest share is addressed first.
Where the time usually goes
When the hardware is the limit
Sometimes it is. A database server given too little memory stays slow however well the code is written. That is checked early, because a hosting upgrade may cost less than a week of engineering.
Frequently asked questions
How much faster will tuning make our application?
It depends on what the measurement finds, and any figure quoted before measuring would be invented. Afterwards, the fixes worth doing are listed with what each one affects.
Does tuning require rewriting the application?
Rarely. Most gains come from indexes, query changes and moving slow work into a background queue, and these leave the rest of the code alone.
The app is slow only at month end. Why?
Usually a reporting query competes with everyday work, or a scheduled job runs at the same hour. Both can be addressed once the timing is visible.
Can you tune a system you do not maintain?
Yes. It is often a standalone piece of work, and your own developer can apply the findings if you prefer.
Tell us what you need.
Share your requirements and one of our engineers will come back to you within one business day.
- No obligation
- A reply within one business day
- Your details stay private
Start with your requirements
Seven short steps that tell us what you need. An engineer reads them before getting in touch.
Share your requirements