Hello, Atlassian Community! I’m Matt Ogle from the Enterprise Product Marketing team, here with the December edition of our Quarterly Performance and Scale Digest. Over the last few months, we’ve delivered multiple performance and scale enhancements to Atlassian Cloud that help your enterprise unlock its full potential.
As business demands grow, so does the need for a platform that scales with your growing organization. Check out our latest scale updates, including the recent Confluence milestone for support of 150,000 users on a single site and a huge new announcement that significantly increases user limits for Jira.
Support for 150,000 users on a single Confluence site is now available
At the end of November we announced that Confluence Cloud Enterprise, Premium, and Standard plans now support 150,000 users on a single site—a monumental 3x increase in scale from our previous user limit. We achieved this milestone by making multiple infrastructure optimizations that enhance efficiency at scale, such as increasing page indexing speeds and automating background tasks. This enables your enterprise to use Confluence as a corporate intranet, fostering greater collaboration across business and technical teams for faster innovation and business outcomes. By uniting more teams on a centralized Confluence space, your organization can confidently scale to meet future demands and ensure knowledge remains accessible across a growing workforce.
Announcing support for 100,000 users on a single Jira site - coming in 2025!
The growth doesn’t stop with Confluence–we are thrilled to announce that Jira will support 100,000 users on a single site in Q2 2025! This 2x increase in scale will empower organizations on Jira Enterprise, Premium, and Standard plans to further accelerate mission-critical work by adding more teams to a centralized site. We can’t wait to see what your teams accomplish when the increased scale of Jira and Confluence are combined.
Discover everything from new features that enable you to optimize site performance to product usability improvements that help you get work done faster.
The Bulk Transition API is now available in Jira, enabling you to transition up to 1,000 issues with a single API call. By automating transitions in bulk, admins and developers save time, minimize errors, and work more efficiently. Closing a sprint becomes effortless when hundreds of completed issues are moved to "Done" in one operation. This is just the beginning—stay tuned for the Bulk Delete API, coming in Q1 2025 to speed up large-scale issue cleanups.
Bulk actions for JSM Portal-only accounts
Bulk actions for managing JSM Portal-only accounts is now available for JSM. This feature saves time and effort for admins managing large volumes of accounts by enabling bulk actions, such as deleting or migrating up to 1,000 accounts simultaneously. For example, admins can quickly delete outdated Portal-only accounts in bulk or migrate hundreds of users to Atlassian accounts during organizational changes, ensuring smooth and efficient service operations.
JQL performance increase for Jira and JSM
As we build towards our Jira 100,000 user scale milestone as previously mentioned, we are future-proofing the Jira Query Language (JQL) capabilities with two backend refinements:
Upgrading Jira’s search backend to meet scale demands for enterprises.
Revamping Jira’s data retrieval APIs to align to industry standards and increase performance and reliability.
These advancements enable you to complete JQL queries faster, with enterprises experiencing the highest performance gains. The new JQL service is rolling out now and will fully replace the previous architecture in 2025.
Faster page load times in Confluence Content Manager
We’ve significantly improved the performance of Confluence’s Content Manager for our largest and most complex customers, cutting average page load times from 23 seconds to just 1 second. By splitting a resource-heavy query into smaller, more efficient subqueries, we ensured that only the necessary data is fetched at the right time. As a result, enterprise space admins can quickly perform critical actions, such as identifying outdated pages to archive, ensuring teams have access to an organized, up-to-date knowledge base at all times.
Improved macro rendering: Macros now render faster in Confluence, making it easier for you to work on pages that contain large volumes of content. Previously, each macro generated its own API request, creating unnecessary browser overhead and occasional page delays or freezes. Now, these requests are batched to significantly reduce the total number of API calls. For our most complex customers, this means that TTVC (Time to Visually Complete) load times for content-heavy pages are more than twice as fast on average.
Macro rendering load comparison before (left) vs. after improvements (right)
Server-side rendering for editor: SSR (server-side rendering) is now enabled for Confluence editor and live page routes, speeding up load times for a smoother experience. By preloading page content on the server, SSR shifts the workload away from the browser so that pages render more efficiently. This results in your Confluence editor and live pages loading faster, slashing the time to display key content in half and keeping teams productive as they navigate pages.
SSR comparison of live page loads before (left) vs. after implementation (right)
Enhanced Smart Links: Confluence Smart Links now deliver a more seamless and visually stable experience. Rendering has been enhanced to preload linked content faster and reduce layout shifts, ensuring a smoother page load. This enhancement supports both first and third-party integrations, such as Jira and GitHub, enabling customers to quickly access critical content and stay immersed while navigating between platforms.
Smart Link load comparison before (left) vs. after enhancements (right)
That wraps up this edition of the Quarterly Performance and Scale Digest! We’d love to hear from you—share your thoughts, questions, or what you are excited about in the comments. Happy holidays!
Matt Ogle
3 comments