Problem Definition

Jira is being used in global companies, which have offices around the globe. Jira can be deployed only in single datacenter, which means users will have large RTT to Jira from another locations.
A couple of examples of network latency:

• Amsterdam (Ams) - New York (NY): 70 ms
• Ams - San Francisco (SF): 150 ms
• Bangalore (BGL) - Ams: 200 ms
• BGL - NY: 290 ms
• BGL - SF: 240ms

Pages can have a lot of related html resources (css, png, js), so due to large RTT total page loading time can be very high.
Currently due to a lot of context specific JS resources, Jira doesn't support caching at proxy level. So that also means it's not possible to use CDN providers (like Akamai , Cloudflare, AWS CloudFront) to optimise access to application, which is typical solutions to the latency problem.

Suggested Solution

• Enable caching for some of static or semi-static resources: CSS, PNG, JS.
• Provide documentation which URLs can be cached and which headers should be respected to prevent caching of user specific or sensitive data

Workaround

There are some examples at Community page, you may want to check if those work for you - CDN-CloudFront-and-Atlassian-Server-apps

Resolution

Starting Jira 8.3, Jira Data Center supports CDN. More details can be found at Content Delivery Network (CDN) for Jira Data Center
After enabling CDN, resources under "/s/..." url will be server from CDN server and not from Jira directly.

Example:

• While loading data from https://bulldog.internal.atlassian.com/browse/PSR-383 (main Jira)
• Jira will return links to to load static data from CDN - https://d2mzx5lfbkaqz9.cloudfront.net/s/.../download/contextbatch/css/_super/batch.css