Current View
File name:

-

File size:

-

Title:

-

Author:

-

Subject:

-

Keywords:

-

Creation Date:

-

Modification Date:

-

Creator:

-

PDF Producer:

-

PDF Version:

-

Page Count:

-

Page Size:

-

Fast Web View:

-

Preparing document for printing…
0%
Service Co. Assures Quality Performance & User Experience During ERP Migration to AWS Enterprise IT teams can learn how a business-to-business services company used nGeniusONE, vSTREAM appliances in AWS, nGeniusPULSE, and Visibility as a Service (VaaS) to find why a new cloud ERP application was five times slower than its legacy version. The case study covers the migration, the analysis of window sizing and TCP problems, and the results. What was the situation? After acquisitions, the company consolidated several management information and enterprise resource planning (ERP) systems into one new ERP hosted in AWS. The legacy ERP ran on servers in field offices and responded in about a second for barcode reading and printing. The weekend after migration, field employees reported waits of six seconds or more, a five-fold increase, which slowed every step of service and order processing. How did IT find the cause? The team had benchmarked the legacy experience with existing ISNG appliances and added vSTREAM appliances in the AWS ERP server farm, with VaaS engineers building dashboards. In the dashboards, Universal Monitor views showed spikes in peak response time and TCP round trip time, and Packet Decode views traced the latency to two combined problems: window sizing issues on some systems in AWS, and a TCP stack problem on some devices that ignored advertised window sizes and sent more data than the other side could receive. What results did the company achieve? With screens and IP addresses as evidence, the AWS partner increased resources and window sizes and fixed the TCP issues. MTTR fell, user experience and productivity improved, and 24x7 VaaS support reduced mean time to know and mean time to restore. The company also reused its nGeniusONE investment for the cloud application. Frequently Asked Questions What did the legacy benchmark show? Field office users saw response times of around a second on a consistent daily basis. Why was evidence useful with AWS? It showed where in the cloud ERP infrastructure the problem was, and specific server IP addresses sped up corrective action. Asset Type: Case Study

About this content