OTRS Slow after upgrade 4.0.5 > 5.0.13

[RiomarGroup]

I'm seeing similar subjects for previous major version upgrades, but I've been using OTRS since the 3.x series and have never experienced a slowdown after the upgrade.

This weekend however I moved to 5.0.13 and my system is almost unusable. I'm not familiar enough with the framework to know where I should even start troubleshooting. The host system is Ubuntu Xenial, running on an AWS t2.micro (1G RAM, 1xXeon 2.4). OTRS is the only this machine does.

We have 2 agents and 10 clients with approx 30 open tickets at any given time. I'm hoping the t2.micro should be enough to run such a small operation. Also, OTRS was not zippy under 4.0.5, but it was certainly manageable.

Any suggestions are appreciated.

[RiomarGroup]

It looks like the issue is memory. I mounted the disk from my server into a t2.small (same CPU, but 2 G of RAM) and the system sped up significantly, it's actually usable. The problem is that I have a reservation for several years on the t2.micro, and we're a low-margin operation, so upgrading my instance would really be a problem. As I mentioned, we have 2 agents working about 30 tickets at any given time. 1G of RAM should really be enough.

Is there anything I can do to on the software side to streamline things? I'm not sure what all has become the memory hog from 4.x to 5.x

[jojo]

2 GB of memory is really needed as the webserver needs memory, the database needs memory and the OS itself also.

[RiomarGroup]

I guess that's the answer then. Upgraded permanently to the t2.small.