• Subject: RE: More AS/400 Web server Load Testing Results
  • From: Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>
  • Date: Wed, 17 Jan 2001 10:39:03 -0800

Title: RE: More AS/400 Web server Load Testing Results

The Freeze was probably do to the initialization overhead of starting 32 more instances plus 500 test jobs.  Change the test jobs to send a transaction every so many seconds for a few iterations.   Have them all start and then delay till a set time, then start firing at the server.  This should give you better server performance testing.  Also a 720 with only 1 gig of memory is probably paging like mad to handle that many jobs.  I would go to 4 gig of memory when the budget allows.

Christopher K. Bipes    mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.        http://www.cross-check.com
6119 State Farm Drive   Phone: 707 586-0551 x 1102
Rohnert Park CA  94928  Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.  Karen Herbelin - Readers Digest 3/2000

-----Original Message-----
From: Stone, Brad V (TC) [mailto:bvstone@taylorcorp.com]
Sent: Wednesday, January 17, 2001 7:38 AM
To: 'MIDRANGE-L@midrange.com'; ign_list@ignite400.org
Subject: More AS/400 Web server Load Testing Results

Anyway, with 100 hits at once the HTTP server started 6 more instance jobs
and the average response time was 2.1222 seconds.

With 500 hits, the HTTP server started 32 more instance jobs and the average
response time was 10.629 seconds.  On this one the machine did seem to
"freeze" for a few seconds most likely from running that many jobs at once.

Any comments?

Brad


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact [javascript protected email address].