From owner-freebsd-isp Tue Nov 19 10:54:33 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA23985 for isp-outgoing; Tue, 19 Nov 1996 10:54:33 -0800 (PST) Received: from i-gw.dalsys.com (i-gw.dalsys.com [207.42.153.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA23972 for ; Tue, 19 Nov 1996 10:54:28 -0800 (PST) Received: (from smap@localhost) by i-gw.dalsys.com (8.6.9/8.6.9) id MAA10133; Tue, 19 Nov 1996 12:54:26 -0600 Received: from future.dsc.dalsys.com(199.170.161.3) by i-gw.dalsys.com via smap (V1.3) id sma010131; Tue Nov 19 12:54:24 1996 Received: from richards.dsc.dalsys.com by future.dsc.dalsys.com (AIX 3.2/UCB 5.64/8.6.12) id AA108417; Tue, 19 Nov 1996 12:59:59 -0600 Message-Id: <32921F9A.48EA@herald.net> Date: Tue, 19 Nov 1996 12:59:06 -0800 From: Richard Stanford Organization: Herald Communications X-Mailer: Mozilla 3.0 (Win16; I) Mime-Version: 1.0 To: dennis Cc: isp@FreeBSD.org Subject: Re: changed to: Frac T3? References: <199611191536.KAA07083@etinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk dennis wrote: > > > >In fact, there is a _great_ deal of painful experience in dealing with > >routers where there isn't quite enough CPU time to get everything done. > >Routing protocols are basically soft real-time distributed systems. When > >they get delayed, they tend to collapse in spectacular ways. As a result, > >putting any significant non-routing load on a router is a _really_ bad > >idea. > > that's 'cause you've been working with machines that have stinky little CPUs > :-) I would hazard a guess that having a couple of large compiles kicked off at the same time would start to cause the routing system a little stress -- no matter what cpu was in the box. Difference would be how long the stress lasted. -Richard