← Back to team overview

launchpad-dev team mailing list archive

how should we make sure new pages meet our performance goals?

 

So a month-and-change back we agreed on this list that we'd make sure
new pages met our performance goals (<1 sec renders 99% of the time, 5
second timeout).

Problem is, I don't think we know how to do that :)

We can rephrase that agreement into a couple of requirements:

 - must have new pages/apis trigger hard timeouts at 5 seconds
 - new pages to trigger soft timeouts at 1 second

The problem is that there is actually a third one:

 - new pages should scale sufficiently well that they don't fall into
trouble immediately that the team project is finished

Some projects will be presenting new views on existing data and these
can reasonably expect that once they are fast enough they will stay at
approximately the same performance for a while. Other projects that
add new data will need to wait for users to come along and well, use
the feature, before we can tell if its scales or not.

So - handling the first two things is pretty easy: I intend to get the
a diff on the PPR and weekly or thereabouts add 5 second hard timeouts
for new page ids. A small patch to do soft timeouts via flags will
take care of the second requirement.

If anyone has ideas on how we can sensibly meet the third requirement
during feature development, please share!

-Rob


Follow ups