Atlassian recommends to perform slow operations during off-peak hours but it seems that they are slow even if these instances are not used at all.
Removing a project with 13.000 issues from an instance with 400.000 issues seems to take more than an hour, even if is running on a machine with 256GB RAM and SSDs. The speed seems to be somewhere around 10-50 issues/second.
Do you know a way to improve performance of project removal in JIRA?
This is a real when you have to split JIRA instances because the XML export/restore is useless because there are no computers that can load this kind of XML into memory.
Excuse me for not specifying that the JVM is configured to use 30GB or RAM, and this instance was used exclusively by one user, just to remove about 100 projects, one by one (scripted, obviously).
The average removal speed was estimated to be 10-20 issues/second. The 32 cores on the machines were clearly not used, as the removal tasks seems to work on a single thread.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs