Upcoming Events

Cloud Connect
Santa Clara
Feb 13-16, 2012

Cloud Connect brings together the entire cloud eco-system to better understand the transformation we're experiencing and promises to be the defining event of the cloud computing industry. Learn about the latest cloud technologies and platforms from thought leaders in Cloud Connect’s comprehensive conference.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up
Network + Systems Management
R E V I E W  
Warding off WAN Gridlock

  November 15, 2002
  By Mike DeMaria


>> continued from previous page

How We Tested

TOC Issue TOC
Printer Print full article
Printer Print this page
Printer Download as PDF
E-Mail E-Mail this URL
flame author Flame the author
 
  In this article
arrow
Introduction
arrow
Don't Say We Didn't Warn You
arrow
Packeteer PacketShaper 4500
arrow
Products Reviewed
arrow
Executive Summary
arrow
Politics, Law and the Traffic-Shaping Admin
arrow
How We Tested
arrow
SIDBAR: Make Your Case
arrow
Report Card

For client machines we used 10 Intel Celeron 500-MHz white box PCs running Microsoft Windows 2000 and an Apple Computer PowerBook G3 connected to the packet shapers at 100 Mbps through an Extreme Summit48 switch, and then to a dual NIC Dell Computer PowerEdge 2450 running Windows 2000 with routing enabled. A T3 (45 Mbps) link was simulated with a Shunra Software's Storm STX-100.

Our server was an Apple Macintosh dual 800-MHz G4 with 1 GB of RAM. We ran FTP, Apache Web server and the Apple Darwin streaming server and used Mercury Interactive's LoadRunner 7.5.1 to generate as many as 100 real TCP sessions. We broadcast "live" a large QuickTime movie set to nonterminating continuous loop. This movie output was, on average, 1.6 Mbps per stream.

LoadRunner let us generate real Windows TCP sessions, and we always ran enough users to oversaturate the T3. Our Web tests included simulating users downloading several multimegabyte pages as well as multiple small pages in succession.

We also tested transferring Web and FTP data simultaneously. We set a policy for a minimum of 20 Kbps per connection with a burst of 50 Kbps, a minimum of 500 Kbps per connection for Web traffic, and 20 Mbps maximum for FTP. We also tested streaming video while concurrently running 100 large Web transfers.


start top   Politics, Law and the Traffic-Shaping Admin SIDBAR: Make Your Case 

Research and Reports

Hypervisor Derby
August 2011

Network Computing: August 2011

TechWeb Careers