3 answers

1 accepted

Also, if you are in VM, if you VM host as powerful as your production?

You can't really trust timing results inside a VM, it's all down to ticks and you can't guarantee that every tick happens when it should. Overall, the result will be fine but at a low level.... it's a bit like quantum mechanics vs newtonian physics

I'd probably go through the upgrade and go straight to 5.2 and do your performance testing there. There is no point fine tuning an environment that you are going to be over-writing straight away

I also count 5 major software changes going on all at the same time, it's never going to be easy to identify the root when so much is changing. Can you not do it as a migration on 3.13 to new software (DB, drivers, test env etc) and benchmark that. Then upgrade to 4.1.2, then to 5.2 & re-do the benchmarks

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

We don't know what your hardware is. The use of VMs, while they have massive advantages, does reduce the chance of like-for-like testing being of much use. Unless your production and test VM servers are separate and pretty much physically indentical and running about the same stuff, comparing two VMs at this level is mostly useless.

Your software is not like-for-like. This is understandable as you are testing an upgrade, but it further compounds the problems from comparing VMs

We don't know much about your MySQL installations - local or remote? Also on VMs? Have you benchmarked them?

One thing that will cause massive disk access on Windows boxes is anti-virus software - have you disabled that on both?

I think a first step might be to forget the upgrade - get a new copy of the live VM and benchmark that with the current software. If it's similar to live, great, you have a baseline. If it isn't the same, then you definitely can't compare them and you might as well give up. Assuming you can, then change one component at a time and re-benchmark. At the moment, you suspect it's Jira (as do I), but you have not ruled out either the database version, the database connector, the operating environment, the database server, etc etc etc

I'm not sure that jumping from 3.13 to 4.1 is the best jump either - I'd have gone for 4.0 or 4.2 myself, but I've not read the docs, so don't quote me.

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...