Case Studies


1. Best Practices in Enterprise Application Performance Management

It’s a summer Friday afternoon and you are just a few clicks away from completing that in-escapable weekly corporate time-sheet application on your PC and head towards the beach. You may even want to squeeze in that much delayed expense voucher, if you have few more minutes left. You are barely through two clicks and the dreaded hourglass makes its appearance. The scenario although not very uncommon, is perhaps not serious enough to warrant filing a trouble-ticket (and besides, you do not want to start that slow Remedy application and risk getting stuck in the rush hour traffic). On the other hand if you are a call center agent and it is taking a minute to pull that customer record, you are in bad luck.
If you are an end-user like that guy headed to the beach or that customer who is just trying to make changes to her return flight, you may not be able to do much- but at least learn to empathize with the complexity of issues if you have a chance to read this white paper.

2. Application Performance Benchmarking During Server Relocation

As a part of its Disaster Recovery strategy, a major regional bank was in the process of moving all servers away from the hurricane-prone area. This server relocation was changing bandwidths and latencies between the end-user machines and the servers/databases and might have resulted in changes to end-user performance, especially for interactive type of transactions.
The bank used OPNET to help track and manage the performance changes by benchmarking response times for representative applications at representative sites before the server relocation. This project briefing describes the steps in the benchmarking effort and how the data was used to mitigate any possible performance issues post-relocation.
Click Here

3. Traffic Baselining Case Studies

Many Small/Medium Enterprises (SMEs) do not implement instrumentation for ongoing monitoring of the WAN links either because of the cost of the devices or the need to dedicate staff. There are always events such as data center relocation, sales-day events, bandwidth abuse, and new traffic patterns that require them to perform at least a one-time traffic baselining to address the immediate business need.
This technical briefing describes several case studies of Traffic Baselining using ACE Live tool (formerly Network Physics). ACE Live’s easy to install and remote-access features, and its rich set of reports from circuit level to TCP level to application level made it an ideal choice for one-time baselining. This briefing demonstrates how each customer had a different business motive for performing the Traffic Baselining and how all of them benefited from the analysis/interpretation of the various charts mined from the ACE Live device.
Click Here

4. Traffic Baselining Case Study

The customer wanted a traffic baseline and analysis of their MPLS-based WAN. The purpose of the baselining/analysis was to validate the customer’s proposed bandwidth upgrades of their data center and some remote links. The customer was also embarking on the deployment of a new version of SAP and had some concerns about additional bandwidth requirements.
A traffic study was conducted by deploying OPNET ACE Live in the data center and collecting data for a week. By setting up appropriate business groups and analyzing the various traffic flows, a comprehensive view of the current status of their network and the pattern of usage by different applications was provided. The traffic study helped the customer to make informed decisions regarding the bandwidth upgrades.
Click Here

5. Performance and Capacity Planning for New Application Roll-out

The customer, a major retail store in healthcare industry was planning to roll out many new applications over its network of several thousand retail stores.
They wanted to ensure adequate network capacity is available for the new applications as well as existing applications. An optimal trade-off between bandwidth at the retail stores and application response time was important because of the huge number of retail stores and associated WAN costs.
Using OPNET, the first application suite was baselined and an analysis/simulation was performed for the various transactions of the application. It was determined that bandwidth and background utilization rather latencies were the major factors affecting the performance. Guidelines were provided for appropriate link sizing in order to meet the desired performance goals.
Click Here