From owner-freebsd-questions Sun Aug 3 12:00:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA09104 for questions-outgoing; Sun, 3 Aug 1997 12:00:30 -0700 (PDT) Received: from ibmmail.COM (ibmmail.com [204.146.168.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA09099 for ; Sun, 3 Aug 1997 12:00:28 -0700 (PDT) Received: from news by ibmmail.COM (IBM VM SMTP V2R3) with TCP; Sun, 03 Aug 97 15:00:25 EDT Message-Id: <3.0.2.32.19970803145947.00920210@mail.gte.net> X-Sender: theta@mail.gte.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.2 (32) Date: Sun, 03 Aug 1997 14:59:47 -0400 To: freebsd-questions@freebsd.org From: Katherine Nenno Subject: FreeBSD and large #s of http requests Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We host a web site for a popular radio show host (#2 in the US, 1 in Canada). Recently (a few months ago), we planned to have a interactive chat with her where people could ask her questions and she could respond. What we didn't count on was the number of http requests this would generate. The site is hosted on a Pentium Pro 200 machine with 64 meg RAM running Apache 1.2.0 and FreeBSD 2.1.7. The chat script was a custom perl script that we contracted out to have written. We didn't anticipate the number of hits that this would generate. Within the first minute the server crashed. Now, we have been asked if we can fix the problem and have another chat that will work. Does anyone have any suggestions on the best way to do this? Is it even possible without buying tons of expensive equipment?