From owner-freebsd-hardware Mon Jun 22 00:48:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10881 for freebsd-hardware-outgoing; Mon, 22 Jun 1998 00:48:34 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from gjp.erols.com (root@alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10857 for ; Mon, 22 Jun 1998 00:48:23 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id DAA13224; Mon, 22 Jun 1998 03:47:51 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Mike Smith cc: "Mr G.D. Tyson" , port-i386@netbsd.org, freebsd-hardware@FreeBSD.ORG From: "Gary Palmer" Subject: Re: O/S Support for large [512Mb] PC systems In-reply-to: Your message of "Sun, 21 Jun 1998 21:33:03 PDT." <199806220433.VAA03531@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 22 Jun 1998 03:47:50 -0400 Message-ID: <13220.898501670@gjp.erols.com> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote in message ID <199806220433.VAA03531@antipodes.cdrom.com>: > Before going any further, you may wish to consider the solutions offered > by NetApp (http://www.netapp.com), as well as the Vixie Enterprises Web > Gateway Interceptor, available from Mirror Image > (http://www.mirror-image.com). The WGI is no more. I heard (unofficially) that the product was pulled. Mirror Image is now selling the Cisco CacheEngine. A rather unremarkable product which apparently most people find deficient. If the person is looking for pure web caches, they may also consider CacheFlow (http://www.cacheflow.com) and Inktomi's Traffic Server (http://www.inktomi.com). The latter is definately a more expensive product, but has more features in the next release (due in a month or so). I've heard a lot of rumours recently, including a multi-threaded version of Squid, backend storage improvements for more speed, etc. So the real decision is what you can best work with. If you don't mind some of the deficiencies of raw squid, and like getting up to your elbows in the code, squid may be a solution. If you are wanting a `fire and forget' solution, then squid may not be for you. (I'm not saying it takes a lot to maintain, but recovery after a crash isn't always as graceful as it should be, etc) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message