Many organizations have their own unique processes and needs. In another case, the custom field count may be huge, while the issue count is small. In one case, the issue count may grow rapidly, while the project count remains constant. Frequently, a few dimensions become significantly bigger than the others. Different Jira instances grow in different proportions of each data dimension. Analytics data shows that nearly every customer dataset displays a unique characteristic. Jira's flexibility causes tremendous diversity in our customer's configurations. Response times for Jira actions Jira 9.3.0 vs Jira 9.2.0 To check the details of these actions and the Jira instance they were performed in, see Testing methodology. The following chart presents mean response times of individual actions performed in Jira. The only difference between the scenarios was the Jira version. We ran the same extensive test scenario for both Jira versions. In this section, we'll compare Jira 9.3.0 to Jira 9.2.0. Jira 9.2 was not focused solely on performance, however we do aim to provide the same, if not better, performance with each release. This page will show how the speed of Jira can be influenced by the size and characteristics of data stored in the database. The operating system, including its file system.The database used and connectivity to the database.The number of jobs and scheduled services.The number of workflow step executions (such as Transitions and Post Functions).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |