From owner-freebsd-isp Sun May 25 16:38:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA15207 for isp-outgoing; Sun, 25 May 1997 16:38:46 -0700 (PDT) Received: from etinc.com (et-gw-fr1.etinc.com [204.141.244.98]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA15198 for ; Sun, 25 May 1997 16:38:42 -0700 (PDT) Received: from dbws.etinc.com (dbws.etinc.com [204.141.95.130]) by etinc.com (8.8.3/8.6.9) with SMTP id TAA25447; Sun, 25 May 1997 19:49:44 -0400 (EDT) Message-Id: <3.0.32.19970525193717.006b5e6c@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 25 May 1997 19:37:19 -0400 To: Intuitive Design Archive From: Dennis Subject: Re: Clients per Bandwidth Cc: Jack Wenger , freebsd-isp@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 01:41 PM 5/25/97 -0400, Intuitive Design Archive wrote: >On Sat, 24 May 1997, dennis wrote: > >> At 01:46 PM 5/24/97 +1000, Daniel O'Callaghan wrote: >> > >> > >> >On Fri, 23 May 1997, Jack Wenger wrote: >> > >> >> I'm trying to figure out how many virtual domains to put on a 128 ISDN >> >> connected box. I've got a P133 w/ 64Mb ram, and a good fast SCSI subsystem. >> >> So, is there a decent way to figure out when I need to move up the >> bandwidth >> >> ladder? >> >> In other words, I wanna know how many concurrent requests I can handle. We >> >> DON'T have anyone dialing in, just hosting web sites. >> > >> >You can work it out yourself. Average request is 10-15 kbytes. >> >128k ISDN can handle 60 MB/hour at 100%. To stay within the comfort range >> >say 30 MB/hour, or 2-3000 requests/hour. >> > >> >It really is pretty basic mathematics, and you should also play around >> >with the figures to work out how much each average request costs you to >> >deliver in bandwidth terms. >> > >> >You should consider selling some *inbound* services (not a lot, but some) >> >or else you will be only half utilising your paid-for capacity. >> >> Its basically a crapshoot (as you only need 1 "killer" site to trash the >> whole >> equation). A bandwidth manager can help eliminate this possibility and >> also allow you to sell chunks of bandwidth and price your services >> accordingly. > > what is a good bandwidth manager. If you don't have access to the >router, or line...? You put the bwmgr inbetween the router and your hosts to be managed. Dennis > > > Intuitive Design Archive > http://www.in-design.com > archive@in-design.com > > > ---------------------------------------------------------------------------- -------- Emerging Technologies, Inc. http://www.etinc.com 56kbs to T1/E1 Adapters for 'BSD and LINUX 4 Port PCI Adapter, 1 or 2 port ISA Adapter ET/BWMGR Bandwidth Allocation Bandwidth Allocation/Limiting Routers