GSX Blog

Validation of Architecture Sizing

Posted by Meryll Moreau on Fri, Sep 20, 2013

After finishing a migration or deployment, a final stress test can be conducted to reveal how the platform will support potential loads. It’s critical to understand if your architecture design can withstand the company’s needs to avoid risking the health of your environment.

Screen Shot 2013 09 20 at 12.02.35 PM

A company has two options to validate architecture sizing. It can either ask the company conducting the deployment/migration for information or ask a third party company to receive an unbiased, expert opinion.

In any case, there is no magic necessary to retrieve this information. Here’s what needs to happen:

  • Discover your Infrastructure needs
  • Analyze how the architecture is being used
  • Validate/optimize the architectural needs to perfectly fit the company’s needs without impacting the cost (and if possible, reduce costs)

In order to analyze your company’s usage, see how users impact the servers, know how the storage is used and learn if the sizing can support daily peaks of change (for example, at 8–9 am when everyone opens their laptop), you will need to receive statistics over a set period of time.

Validating the architecture sizing wouldn’t be useful if you only looked at a short period of time. You need enough context to make a smart decision that will sustain your environment.

The ideal situation would be to constantly collect information to view and understand the environment’s status in real-time. A tool that consolidates this data and delivers user-friendly reports can provide you with a unique analysis of trends and forecasting features that will significantly optimize the infrastructure.

Has your migration or deployment been a success? Will you consider following the recommendations of this article? I would love to hear about your experience in the comments below!

Tags: GSX Monitor, Migration, Audit, Architecture Sizing