nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Will moving 10-20k issues have an impact on long term performance?

Seb Kouba

We are looking to move around 10-20k issues between JIRA Projects. I was wondering if we should worry about the performance impact this may have, since each issue will end up being accessible via two issue keys (with associated db entries).

Does anybody have any experience with this or can comment in general?

We have 40k issues in total and would expect our current hardware to manage 150-200k issues.

Cheers

Accepted answers

Timothy

I do not believe that there would be a significant performance problem. Once moved, I am quite sure that your users will start forgetting about the old issue keys and start using the new ones.

All comments

Timothy

I do not believe that there would be a significant performance problem. Once moved, I am quite sure that your users will start forgetting about the old issue keys and start using the new ones.

Nic Brough -Adaptavist-

I'd echo that. You'll find the server grinds while you do the move, but once it's complete, you won't notice any performance impact at all. In terms of data, all you've really done is add one more item to the index for each of the moved issues, and that item is only really used when a user hits one particular situation when looking at a single issue. So it's negligible.

Seb Kouba

Thanks to both of you! I wanted to check because think our moving around isn't actually critical but if Jira can handle it I guess it's fine.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira