archiving older issues for system optimisation

[Marius Dinca]

We run service desk 3.11 on jira 7.8.0 in server instance, we currently have around 20k issues and its starting to run a little slower, so we will need to archive some older issues.

Is there a way we can archive them but still have access to them? or the only way to improve performance is deletion?

Thanks.

[Alexey Matveev]

Hello,

20K issues should not influence performance. You need to find out the real reason.

[Marius Dinca]

I run it on a VM with 4 xeon cores and 16gb ram, i gave the tomcat vm 2GB.

Sometimes Zabbix agent tells me it has some sql related issues like locks, timeouts.

And in resource monitor i see tomcat using 50% CPU constantly.

LE

also, performance means that we wait about 5ish to 10 s sometimes for it to finish sending a comment or perform a transition

[Alexey Matveev]

Something is wrong with your system. You should investigate it. If you have any add-on installed, you should disable them first and see how it works.

You can find more info here:

https://confluence.atlassian.com/conf65/performance-tuning-939701906.html