| Excerpt | ||||
|---|---|---|---|---|
| ||||
Here are the results of our performance tests. |
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
InformationThese are the results of our performance tests. If your performance is sensitive and/or you are working on server sizing, it may be better that you perform performance tests on a staging instance yourself. |
...
150 requirements per page, with a maximum of 400 (Confluence doesn't support infinite pages anyway).
The default Global Limit is 12,000 and it should be the optimum for most people. If administrators notice that the ConflueConfluence is running slow, this might be where you need to check first.
The expected number of dependencies, as explained on Limitations, is about 20. We don't have a hard limit, but please don't design a model with 1000-to-1 relationships, whether on requirements or on Jira issues.
The size limit for baselines depends on the Global Limit and it is 12,000 requirements by default.
...
Use queries that return fewer requirements, in the search, but more importantly in the dependency, traceability and coverage matrix.
The dependency matrix and the coverage report can only be built by users who can export the space (This permission will change in version 2.0, see Release Notes 2.0).
Therefore, inform a subset of your users about the server limits and the tips to prevent a memory overflow; and restrict the export permissions to this group only.
As a last resort, don't use the coverage and dependency matrixes. You can always explore Confluence's database schema and run the queries using an SQL tool. Tables related to Requirement Yogi start with "AO_32F7CE_AOREQUIREMENT".
...