|
It must be the hardware capacity. The 170 we're using is: CPW Batch: 114 - Inter: 23 Memory: 128 MB So it was probably the 4000 to 5000 hits in that 60 to 90 minute window that brought it to its knees. Thanks everyone... I hope to move to a V5Rx machine this year using Apache. -Bob Cozzi www.rpgiv.com -----Original Message----- From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Joel Cochran Sent: Thursday, January 06, 2005 2:47 AM To: Web Enabling the AS400 / iSeries Subject: Re: [WEB400] Hit capacity of Classic HTTP Server and a module 170 On Wed, 2005-01-05 at 23:26, Bob Cozzi wrote: > Hi, > This morning my little old 170 running IBM's Classic HTTP Server on OS/400 > V4.5 "crashed". > Can the 400 handle 5,000+ to 10,000+ hits per hour on an entry-level > machine? > -Bob Cozzi Bob, When we started http://www.vamanet.com in 2001, we were running a similar system. It only took a couple of months (with relatively little traffic) to figure out that this entry level machine couldn't handle more than a few simultaneous requests. The system would quickly just come to a halt, and page delivery time became completely unacceptable. Since then, we have been running a dedicated 270 with 1100 CPW and no interactive processor. I don't have any real numbers for you, but we run between 50,000 and 100,000 hits per day, usually with no real problems. Joel http://www.rpgnext.com _______________________________________________ This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/web400 or email: WEB400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/web400.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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 on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.