Remedy upgrade – pre and post upgrade performance compared.
We undertook a short exercise for a client recently, putting some monitoring in place on their Remedy 9.1 prior and after a hardware upgrade.
We set up end user monitoring of certain response times using the Scapa Test & Performance Platform. A simple transaction was recorded and automatically parsed to be able to be executed unattended. We logged into Remedy, opened the Incident Console, did a search on a specific criterion and exited.
The monitoring was set up to run for a few days pre and post upgrade. The graph below shows the output, including the down period where the upgrade was being performed.
There was a noticeable improvement in performance post upgrade. The overall response time (green line) dropped to an average of about 31seconds, from an average of around 40, with peaks of 50 seconds. Similarly, the subsequence transactions all improved post upgrade, particularly the timers for login and search, while the variation in these response times is pretty much ironed out.
Quite aside from the specifics of this upgrade, we wanted to show how a quick and easy monitoring set up can be introduced, and the benefits easily quantified using Scapa TPP.
Please get in touch if you’d like to implement anything similar.