Performance testing for AEM 6.5 on premise.

@npalani1 

One should perform the performance testing on the upgraded environment. This is to assure that the system is better at par if not better than the previous system.

Ideally, we should optimize the environment to have better performance to appreciate the benefits that the new environment provides. It will also help you to revisit, if any item was missed in previous environment.

Please assure you cover:

- Integrations

- Frequently used features

- Memory intensive operations

Hi @npalani1 

It is generally recommended to perform performance testing after an upgrade to ensure that the upgraded environment meets the required performance criteria. While it may be tempting to skip performance testing after an upgrade, it is important to consider the potential impact of the upgrade on the performance of your AEM instance.

Upgrading to a new version of AEM can introduce changes in the underlying infrastructure, which may impact the performance of your application. These changes can include improvements in performance, bug fixes, or even changes in default settings that may affect performance.

By performing performance testing after the upgrade, you can identify any performance regressions or issues introduced by the upgrade. This allows you to proactively address any performance bottlenecks or configuration changes that may be required to optimize the performance of your application in the upgraded environment.

Skipping performance testing after the upgrade may lead to unexpected performance issues in the production environment, which can negatively impact user experience and overall system stability.

Therefore, it is recommended to include performance testing as part of your upgrade process to ensure a smooth transition and to validate the performance of your application in the upgraded environment.

Why would one conduct performance testing in an environment that is about to undergo changes, such as an upgrade? The primary objective is to establish a performance baseline before the upgrade. By running performance tests before the changes, you can understand how the current environment is performing.

Once the upgrade is complete, it is advisable to conduct performance tests again. This post-upgrade testing allows you to assess and compare the performance of the modified environment with the baseline. The comparison helps identify any improvements, degradation, or potential issues introduced by the upgrade. Therefore, the overall process involves pre-upgrade testing to establish a baseline and post-upgrade testing to evaluate the impact of changes on performance.

@npalani1 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.