Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How many tasks are too much for Jira to handle

We have an application in the works that creates Jira tasks for incoming work.  Does anyone have an idea what the limits are on numbers of tasks?  This application could potentially be creating hundreds or even thousands of tasks per day.  



Darin --

1 answer

1 accepted

Hi Darin,

That is one heck of a question and use case. My gut wants to say that you're using Jira incorrectly, but I do not know the whole of your situation to pull that trigger.

Nobody knows the actual limit. It can vary a lot due to resources, number of fields, automation in the instance, and any number of other items. Could you scale all resources up sufficiently to hit the actual maximum? Probably. What would the be the limiting factor? Probably a database table constraint or database specific numeric limit on a column or some other unicorn fart buried somewhere in the coding.

The bigger problem is the number of concurrent requests being made. The bottlenecks are writing to the database, updating the index, and the data getting to the two previously mentioned bottlenecks. You can throw resources at it, but there is generally a budgetary constraint. You can tune the configuration, add more nodes, direct all traffic from that app to a single node, and apply all the magic a team of keyboard wizards can provide; but you will always hit a point of diminishing returns.

Oof, oh yeah. I see sever in the upper right of this post. There will likely be slowdowns in the UI for human users when that app is either creating zero or a lot of requests even if you have everything tuned exactly correct.

I hope that answers your question. Cheers!

It does help some.  And yes, I've also got a question in on the best practices for Postgres for this Jira instance.    I figure it will come down to database commit performance.  I'm pretty much sold on a RAID 10 array for the database alone.. I'm also looking into internal Postgres tuning as well.



Like Joshua Sneed _ Contegix likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

270 views 13 14
View question

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you