Maybe number of issues is not a problem but all actions around issues.. yes, it is! You can have 1 milion issues but only 1 single active user and this will work smoothly but when your real time users number increase and those users have their own dashboards, searches, subscriptions, boards, add, remove, .. just be active and use system as usual then it is starting to make things slow.
Some time ago we did with a couple colleagues a JIRA test to answer a question how much issues JIRA can handle? .. We had very powerful machine with many CPU cores, more than 32GB machine etc. and created 18 milion issues (and creating was not a problem) .. what happen after that? ... for example .. Dashboard opened around 20 min :) . Operations were possible but that is not how JIRA should be used. And we only used few active users at the same time. I do not even say how long a reindex took :) ..
So one node is not good option if you want to go with "milions" of issues. How this would be working on multiple nodes? It is a open question but it still might be not super fast. Everything depends on how instance would be used and infrastructure behind. I recommend do not think about this now just scale when there is a need. Add resources and nodes and then react if you see any slowness. You can always archive some projects.. and maybe some day JIRA would have a cool performance improvements that do not exist now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.