From: Matt Clark <matt@ymogen.net>
To: Bruno Wolff III <bruno@wolff.to>
Cc: Kent Anderson <kenta@ezyield.com>
Cc: 'Pgsql-Admin@Postgresql. Org' <pgsql-admin@postgresql.org>
Subject: Re: NIC to NIC connection
Date: Wed, 20 Oct 2004 06:54:31 +0100
Message-ID: <4175FD97.4080500@ymogen.net> (raw)
In-Reply-To: <20041019223345.GA3753@wolff.to>
References: <LPENJIOOLAIJBFKIBDKOAEJHFMAD.kenta@ezyield.com>
<00d001c4b5f9$f4d63660$8300a8c0@solent>
<20041019220133.GA2957@wolff.to>
<41759198.4070505@ymogen.net>
<20041019223345.GA3753@wolff.to>
>>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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: matt@ymogen.net, bruno@wolff.to, kenta@ezyield.com
Subject: Re: NIC to NIC connection
In-Reply-To: <4175FD97.4080500@ymogen.net>
References: <LPENJIOOLAIJBFKIBDKOAEJHFMAD.kenta@ezyield.com> <00d001c4b5f9$f4d63660$8300a8c0@solent> <20041019220133.GA2957@wolff.to> <41759198.4070505@ymogen.net> <20041019223345.GA3753@wolff.to> <4175FD97.4080500@ymogen.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox