pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rusty Conover <rconover@infogears.com>
To: Ross J. Reedstrom <reedstrm@rice.edu>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: TCP network cost
Date: Tue, 17 Feb 2009 00:20:02 -0700
Message-ID: <3FAF940B-9B0B-4DBA-8728-6096022129DF@infogears.com> (raw)
In-Reply-To: <20090217070403.GB2486@cooker>
References: <20090217070403.GB2486@cooker>


On Feb 17, 2009, at 12:04 AM, Ross J. Reedstrom wrote:

> Recently I've been working on improving the performance of a system  
> that
> delivers files stored in postgresql as bytea data. I was surprised at
> just how much a penalty I find moving from a domain socket  
> connection to
> a TCP connection, even localhost. For one particular 40MB file  
> (nothing
> outragous) I see ~ 2.5 sec. to download w/ the domain socket, but ~  
> 45 sec
> for a TCP connection (either localhost, name of localhost, or from
> another machine 5 hops away (on campus - gigabit LAN) Similar numbers
> for 8.2.3 or 8.3.6 (on Linux/Debian etch + backports)
>
> So, why the 20 fold penalty for using TCP? Any clues on how to trace
> what's up in the network IO stack?

Try running tests with ttcp to eliminate any PostgreSQL overhead and  
find out the real bandwidth between the two machines.  If its results  
are also slow, you know the problem is TCP related and not PostgreSQL  
related.

Cheers,

Rusty
--
Rusty Conover
rconover@infogears.com
InfoGears Inc / GearBuyer.com / FootwearBuyer.com
http://www.infogears.com
http://www.gearbuyer.com
http://www.footwearbuyer.com

view thread (23+ messages)  latest in thread

Message-ID: <3FAF940B-9B0B-4DBA-8728-6096022129DF@infogears.com>
Permalink:  ../3FAF940B-9B0B-4DBA-8728-6096022129DF@infogears.com/
Also on:    postgresql.org/message-id/3FAF940B-9B0B-4DBA-8728-6096022129DF@infogears.com

 · 

reply

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: rconover@infogears.com, reedstrm@rice.edu
  Subject: Re: TCP network cost
  In-Reply-To: <3FAF940B-9B0B-4DBA-8728-6096022129DF@infogears.com>

* 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