In my mind it's clear, when I see those animations, that it will be slower. Maybe it will even have a splash screen with a progress bar.
Miss those robots on the spin up screen that you might remember from that past?
It's getting a lot faster. We're going to keep going.
That would be understandable (though hardly acceptable) for an SPA, but this is Enterprise, where every navigation still requires a full reload, and the page you're actually looking for (the issue page) is never less than 3 links away from the useless dashboard that some designer put in because that's what all the cool kids do.
How did this shit get past QA? Did the QA people give up on trying to file any issues because the UI was so slow? Do all developers at Atlassian have a Stockholm Syndrome that would put Microsoft to shame? That this actually made it through development (nevermind that it somehow has paying users) is absolutely mind-boggling.
* elastic scaling, * large in-memory caches like memcached, * data locality, * alternative data stores better suited to our data structures such as dynamoDB, * different instance sizes, * dedicated asynch batch processing nodes, * specific instance sizes suited to specific workloads, etc etc
We are also optimizing how and where we store data. We are already storing data in different AWS regions (closer to our customers), however, we are going to also start getting smarter about ensuring the data is actually in the optimal region for the majority of users on a site.
There is also room for improvement in tuning how we query data for issues with many fields, or instances with very with complex permissions enabled. This will require optimizing the SQL we use to retrieve data, to provide all we need to render a Jira issue as fast as possible and exploring other storage technologies for fast data retrieval.