From owner-freebsd-isp Fri May 23 10:57:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA05043 for isp-outgoing; Fri, 23 May 1997 10:57:32 -0700 (PDT) Received: from wild.net (Cheetah.Wild.Net [207.43.194.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA05035 for ; Fri, 23 May 1997 10:57:29 -0700 (PDT) Received: (qmail 27192 invoked from network); 23 May 1997 17:56:54 -0000 Received: from cheetah.wild.net (207.43.194.2) by cheetah.wild.net with SMTP; 23 May 1997 17:56:54 -0000 Date: Fri, 23 May 1997 12:56:53 -0500 (CDT) From: Kenny Elliott Reply-To: Kenny Elliott To: "Gary D. Margiotta" cc: Livingston Portmaster Users List , freebsd-isp@freebsd.org Subject: Re: data caching In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I would suggest you take a look at Squid (http:/www.nalar.net/Squid). It's a proxy that will cache http, wias, ftp, and gopher requests. We have used it here to cut down our web traffic by 30%. Not a tremendous help but every little bit helps. On Fri, 23 May 1997, Gary D. Margiotta wrote: > Hello, > > This might be a stupid question, and if it is, I apologize. I have a > Portmaster PM-2e20 for my terminal server, and all of our machines run > FreeBSD, most with 2.2.1-Release right now, which is why I'm posting to > both lists. > > What I would like to know is this: > > We have a small dedicated line right now, 128k FR, but we have usually > around 15-20 users on during peak times. Since our line technically can't > handle that many simultaneous users pulling data at 28.8+, is there a way > to use the line more efficiently by caching all data going into and out > our line. > > What I'm basicaly saying is that since modems pull at, say average 4k/sec, > is there a way for all data to be dumped into cache either on the > portmaster or on one of our machines so that the data can get to us faster > and the line can go on to getting something else, while having the users > pull at a nice rate since now the data is local. The data will get dumped > locally faster, and that will allow something else to go or come over the > line instead of trying to carry 20 simultaneous pulls for each of the > users, while trying to handle mail and the various web hosts we have. I > know apache can cache data for the html transfers, but I don't know of > anything that might be able to do this, if there is such a thing. > > Thanks in advance for any answers you have. > > -Gary Margiotta > TBE Internet Services > http://www.tbe.net > \/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/ Kenny Elliott System Administrator Wild.Net L.L.C. http://www.wild.net 504-875-9453 PGP public key available at http://www.wild.net/~kenny/PUBLIC.key \/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/*\/