Before migrating, what should be done to compare performance?

Before migrating, what should be done to compare performance?

• A. Run stress tests
• B. Create performance baselines
• C. Take baselines
• D. Back up data

Answer: (C)

Setting a performance baseline before migrating gives you a reference point to compare post-migration results. This means taking measurements of key metrics—such as latency, IOPS, throughput, and CPU/memory usage—under representative workloads in the current environment. With these baselines, you can evaluate how the new environment stacks up after migration and quickly identify regressions or improvements. While stress testing can be valuable, it’s typically part of validating the system under heavy load after migration, not the baseline capture. Creating performance baselines can be useful in planning, but the essential action is to actually take measurements. Backing up data is crucial for safety, but it doesn’t establish a performance reference.

Setting a performance baseline before migrating gives you a reference point to compare post-migration results. This means taking measurements of key metrics—such as latency, IOPS, throughput, and CPU/memory usage—under representative workloads in the current environment. With these baselines, you can evaluate how the new environment stacks up after migration and quickly identify regressions or improvements. While stress testing can be valuable, it’s typically part of validating the system under heavy load after migration, not the baseline capture. Creating performance baselines can be useful in planning, but the essential action is to actually take measurements. Backing up data is crucial for safety, but it doesn’t establish a performance reference.