Performance of New Servers @ the ACL

Cesar Cavazos

Accounting Information Technology (AIT)

Agenda

• Introduction / Problem Description

• Background Information

• Possible Solutions

• Solution Chosen

• Testing / Analysis

• Future Work / Conclusion

Problem Description

• Large Number of Students

• Problems with old servers

• New Servers– 18 new Poweredge 2650 servers– 3.2 Ghz– 4 Gigs of Ram

• Help CS Department

Background Information

• Dr Baker, Dr. Camden, Alberto Alonso

• Always had the interest in testing servers

• Limited experience working with servers

• Performance is a way too broad test

• Network bandwidth testing

• Other testing done

Possible Solutions

• Different tools out there– Silkperformer– LoadRunner– TestStudio– WCAT– JMeter

• Cost of each testing tool

• Limitations

Solution to Problem

• Use JMeter to test performance– Java Application– Simulate Heavy Load on Server– Performance of Static and Dynamic Resources– FTP Testing– Easy to use GUI– Graphical Analysis of Results

JMeter Interface

Generating Testing Files

Testing Website

Uploading Data to Server

Checking for Errors

Testing Different Combinations

Results of Project

Results Analysis

• Software installed preventing more than 100 connections

• NFS (Network File System) crashed before webserver. (150 connections)– Currently running NFS version 2

• Many limitations compared to version 3• In the process of being installed

• Lab Administrator surprised about NFS acting as a bottleneck

Future Work

• Be able to run JMeter as a Webapp using Tomcat.

• Test the SFTP server (when JMeter implements that option)

• Test the servers when they install NFS version 3 and check performance

Conclusion

• There are many limiting factors involved– Jmeter itself– Fact that it is a single computer– No tool can really simulate ‘x’ number of different

users from one computer

• NFS Protocol

Questions?