Since our plugins work with Jira the first thing to consider is theJira Sizing Guide. The additional footprint our plugins add is difficult to estimate due to the various possible configurations of modules and functionalities that can be used. 20 to 30 per cent more powerful servers should be safe to assume if you want to ensure comfortable interaction while working with our plugins.
We do not support HSQL and H2 databases. The plugin should work on them, but some bugs may happen and we cannot guarantee a smooth experience. The recommended databases are MSSQL, MySQL, PostgresSQL and Oracle.
When it comes to responsiveness, the end-user PC has impact. Having an updated Chrome or Firefox on a modern PC (dual-core PU, preferably at least a Sandy Bridge series for Intel and at least 2 GM RAM, preferably 3-4) is advised.
For the following table, notice that the order is not exact because Clocks are listed to give an idea of specific workload requirements. With the same clocks number, obviously an i5 will be more powerful than an i3. THis is actually more of a matrix than a table.
Core i5-class CPU
Core i3-class CPU
Core i7-class CPU
The figures above are for Sandy Bridge and newer generations of Intel CPUs. Equivalents for AMD and other manufacturers vary, it is best to consult your server provider or administrator.
BigPicture performance tests conducted by SoftwarePlant
SoftwarePlant performs load and performance tests before each release to maintain optimal user experience of BigPicture. Details of Jira environment used for performance tests:
Operating System: Linux
Jira RAM: 1536 MB - for plain Jira and BigPicture
CPU of the host server: 8 cores - host server manages the CPU allocation
Maximum number of Jira issues
Performance tests executed by SoftwarePlant have set the threshold of issues possible to present by a single BigPicture Program to 10000 issues.
Jira server memory setup comfortable for BigPicture
The general rule of thumb is to preserve 4KB of RAM memory for each Jira issue registered in the system.
This conversion formula includes overhead which is generated by BigPicture entities that accompany BigPicture tasks (which are entities wrapping Jira issues).
For a Jira instance with 200k Jira issues, 650 Custom fields, 185 issue types, 185 workflows, 2500 users.
For issues, always remember about the 4KB per issue rule of thumb.
All 650 custom fields can be used in a Program Perspective configuration. Number of columns has a direct impact on the BigPicture performance and Gantt loading speed.
Issue types, workflows, and users do not influence the performance of BigPicture.
BigPicture Gantt automatic WBS
Configuring synchronisers in any Program synchronization configuration directly affects the performance of BigPicture when opening a Gantt.
Each synchronizer adds additional work performed for every Jira issue in the scope of a Program.
If you configure your Jira based on best practices as described above it will ensure successful implementation of BigPicture into your environment.
"Are there any special configurations related to performance, is it possible to maybe reserve more threads for BigPicture? Or similar..."
Here are some tips that might help:
use Use date filtering if your program spans long period of time