"Performance warning"

Łukasz Modzelewski

Performance warning” is being displayed whenever you set up a Scheduled Issue that is set to be executed every one hour or more often. The idea behind it is to find Scheduled Issues that are being executed very often, so that JIRA administrators can identify them and then possibly optimize their schedules in order to minimize the server load. It is not documented in the wiki page (however, it should be, we’ll try to take care of it soon), but it is simply a way of informing the users that multiple triggers with very short time interval may lead to decreased JIRA performance.

The reason for that is that "The Scheduler" add-on simply creates new issues (much like an ordinary JIRA user would) as per the trigger configuration (which could be as seldom as once a year, and as often as every minute). In general, most of our customers are happy with The Scheduler performance, however, if there are many Scheduled Issues, which triggers interfere with one another (like “execute every day at 9am”), you may experience performance degradation during such a time. That being said, since it depends on both your JIRA server setup and your particular Scheduled Issue triggers, the actual performance depends heavily on your particular use-case.

As per your use-case (looks like you’re going to have a lot of triggers), we’d recommend you to estimate (roughly) how many Scheduled Issues are you going to create, and then categorize them into “similar” buckets - like “end-of-each-month”, “beginning-of-the-week”, “each-morning” etc. Then, try to distribute the execution times of each Scheduled Issue in the bucket so that they do not all start at the same time.

I hope this explanation clears out your doubts.

2016-09-15T09:15:24+00:00

Comments (6)

Łukasz Modzelewski
- changed status to open
- 2016-09-15T09:14:30+00:00
Łukasz Modzelewski
Performance warning” is being displayed whenever you set up a Scheduled Issue that is set to be executed every one hour or more often. The idea behind it is to find Scheduled Issues that are being executed very often, so that JIRA administrators can identify them and then possibly optimize their schedules in order to minimize the server load. It is not documented in the wiki page (however, it should be, we’ll try to take care of it soon), but it is simply a way of informing the users that multiple triggers with very short time interval may lead to decreased JIRA performance.

The reason for that is that "The Scheduler" add-on simply creates new issues (much like an ordinary JIRA user would) as per the trigger configuration (which could be as seldom as once a year, and as often as every minute). In general, most of our customers are happy with The Scheduler performance, however, if there are many Scheduled Issues, which triggers interfere with one another (like “execute every day at 9am”), you may experience performance degradation during such a time. That being said, since it depends on both your JIRA server setup and your particular Scheduled Issue triggers, the actual performance depends heavily on your particular use-case.

As per your use-case (looks like you’re going to have a lot of triggers), we’d recommend you to estimate (roughly) how many Scheduled Issues are you going to create, and then categorize them into “similar” buckets - like “end-of-each-month”, “beginning-of-the-week”, “each-morning” etc. Then, try to distribute the execution times of each Scheduled Issue in the bucket so that they do not all start at the same time.

I hope this explanation clears out your doubts.
- 2016-09-15T09:15:24+00:00
Łukasz Modzelewski
- changed status to resolved
- 2016-09-15T09:15:33+00:00
Former user Account Deleted reporter
Great explanation, but it doesn't give me concrete numbers to use as a reference. What kind of Jira performance was your local performance test showing + the server specs. Could that be put in a document page? If yes, and when ready please send me a link to that. Tx Łukasz!
- 2016-09-20T19:24:03+00:00
Former user Account Deleted reporter
- changed status to open
- 2016-09-21T15:53:41+00:00
Łukasz Modzelewski
Issue ~~#285~~ was marked as a duplicate of this issue.
- 2018-01-08T07:32:45+00:00
Log in to comment