X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B9C0A32A93D for ; Wed, 20 Oct 2004 06:54:38 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 98038-05 for ; Wed, 20 Oct 2004 05:54:35 +0000 (GMT) Received: from bayswater1.ymogen.net (host-154-240-27-217.pobox.net.uk [217.27.240.154]) by svr1.postgresql.org (Postfix) with ESMTP id 07BFA32A8EB for ; Wed, 20 Oct 2004 06:54:34 +0100 (BST) Received: from [82.68.132.233] (82-68-132-233.dsl.in-addr.zen.co.uk [82.68.132.233]) by bayswater1.ymogen.net (Postfix) with ESMTP id 53CB7A3D2F; Wed, 20 Oct 2004 06:54:31 +0100 (BST) Message-ID: <4175FD97.4080500@ymogen.net> Date: Wed, 20 Oct 2004 06:54:31 +0100 From: Matt Clark User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruno Wolff III Cc: 'Kent Anderson' , "'Pgsql-Admin@Postgresql. Org'" Subject: Re: NIC to NIC connection References: <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> <41759198.4070505@ymogen.net> <20041019223345.GA3753@wolff.to> In-Reply-To: <20041019223345.GA3753@wolff.to> Content-Type: multipart/alternative; boundary="------------060109020209050809020806" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.0 tagged_above=0.0 required=5.0 tests=HTML_20_30, HTML_MESSAGE, HTML_TITLE_EMPTY X-Spam-Level: * X-Archive-Number: 200410/254 X-Sequence-Number: 15247 This is a multi-part message in MIME format. --------------060109020209050809020806 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit >>If you have 6 app servers it's just daft to stick 6 NICs in your DB >>server. >> >> > >While there might be some cases where that makes sense most likely it >isn't something you would want to do. I believe the original motivation >was to solve bandwidth congestion rather than security. > > > If the NICs are saturated then channel bonding is the answer. Any modern switch and OS will let you bind together multiple NICs so they appear as one. You can get an 4Gbps link this way. --------------060109020209050809020806 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit
If you have 6 app servers it's just daft to stick 6 NICs in your DB 
server.
    

While there might be some cases where that makes sense most likely it
isn't something you would want to do. I believe the original motivation
was to solve bandwidth congestion rather than security.

  
If the NICs are saturated then channel bonding is the answer.  Any modern switch and OS will let you bind together multiple NICs so they appear as one.  You can get an 4Gbps link this way.
--------------060109020209050809020806--