What is the pricing for the Data Center version?
The pricing is exactly 25% of Confluence for each tier, except the lower tiers where it is the price of the Server version. At the time of writing:
|Tier||Confluence DC||Requirement Yogi DC|
|... etc. The latest price information can be found on our product page.|
What is our progress on Data Center compatibility?
Progress : DONE!
Approved on August 7th, 2019.
Approved in 2019.
What is our version support policy?
We follow Atlassian's Long Term Support release policy: We support those versions for 2 years.
|Product||Version||First published||Supported until|
What is our escalation process?
What is our detailed progress?
We've given performance information on the page Performance.
|Work on cluster|
Yes for Confluence.
Yes for Jira.
|Testing performance with thousands of records.|
We've tested the performance in the browser for 1000 pages of 300 requirements each and it performs well. Administrators can use the Global limit to limit the number of requirements that can be managed in a single document.
We've tested the performance on the server for 1500 pages of 500 requirements each. It performs well. We keep this information in the page named Performance.
|Testing performance with millions of records, on an AWS deployment.|
We've tested with 1 million pages (with or without requirements) and 1 million requirements.
|Solving performance bottlenecks.|
All Confluence bottlenecks have been solved, notably the global limit, which was implemented a few months ago.
The Jira implementation was entirely changed to support a queue.
We have noticed our upgrade tasks and REST resources use a single Hibernate session despite the "flush session" instruction that we perform at each saving point. There is no way around this.
|Submitting results to Atlassian to get the DC certification.|
Success, for Confluence, PSEA and Jira.
The "Test & Compliance" module will not have a "Data Center" version. This module is not generally used by Data Center customers.
|Provide a clear escalation process for customers.||See our escalation process.|
Performance issues we've identified
No impact on pages which don't use Requirement Yogi
Our app has very little impact on pages or issues without Requirement Yogi (It only performs 1 SQL query per page load, 1 SQL query per issue in Jira).
|A customer tried to create 1500 requirements on a single page, and the editor is slow.|
This is not due to Requirement Yogi.
If one creates a Confluence page with a table of 1500 lines containing "Status" macros, which are native to Confluence, then they get the same performance.
|The search screens (traceability matrix, dependency matrix, etc) require resources to build.|
|Large hibernate sessions: We've noticed that Confluence doesn't respect our instructions to flush the transactions when we order them.|
* A "Requirement" is a line in the table of a requirement document.