This rule is currently archived
Archived Reason: archived as duplicate
Do you establish a baseline?
28/08/2019 9:14 AM by
most important part of performance tuning is being able to quantify the process. This is why it’s super important that before you touch any code or SQL, that a measurement be taken of the current performance. Now the general rule is to make sure the tests are being run on the same or similar hardware to production and that the test always be run on the *same infrastructure* - otherwise you’d be comparing apples with oranges .
Once you establish that baseline, you can then incrementally measure the performance impact for each change being made. This way you can measure effort vs reward as you could be working on a tweak for weeks that only improves performance by a few milliseconds whereas spending an hour to bundle and minify assets might yield a 50% improvement.
Do you feel this rule needs an update?