pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron Johnson <ron.l.johnson@cox.net>
To: PgSQL Performance ML <pgsql-performance@postgresql.org>
Subject: Re: x86-64 and PostgreSQL
Date: 20 Jan 2003 03:52:15 -0600
Message-ID: <1043056334.15592.167.camel@haggis> (raw)
In-Reply-To: <3E2BE4BF.28150.D33005A@localhost>
References: <1042867764.889.181.camel@haggis>
	<3E2BE4BF.28150.D33005A@localhost>

On Mon, 2003-01-20 at 00:29, Shridhar Daithankar wrote:
> On 18 Jan 2003 at 11:39, Andrew Sullivan wrote:
> > On Fri, Jan 17, 2003 at 11:29:25PM -0600, Ron Johnson wrote:
> > > Hi,
> > > 
> > > Will there be any advantages to running Pg on a 64-bit CPU rather
> > > than 32-bit?
> > 
> > In my experience, not really.  We use SPARCs under Solaris 7 and,
> > now, 8.  We haven't found any terribly obvious advantages with the
> > system compiled as a 64 bit app, but we _did_ find problems with the
> > 64 bit libraries combined with gcc.  As a result of that and
> > pressures to get working on some other things, we stopped testing
> > Postgres as a 64 bit app on Solaris.  We haven't done any work on
> > Solaris 8 with it, and that system is a little more mature in the
> > 64-bit-support department, so when I have a chance do to more
> > investigation, I will.
> 
> I remember reading in one of the HP guides regarding 64 bit that 64 bit is a 
> tool provided for applications. In general no app. should be 64 bit unless 
> required. In fact they advice that fastest performance one can get is by 
> running 32 bit app. on 64 bit machine because registers are wide and can be 
> filled in is less number of fetches.
> 
> Sounds reasonable to me.

Dou you, the programmer or SysAdmin, always know when 64 bits is
needed?

Take, for simple example, a memcpy() of 1024 bytes.  Most CPUs don't
have direct core-core copy instruction.  (The RISC philosophy, after
all, is load-and-store.)  A 32-bit executable would need 1024/32 = 32
pairs of load-store operations, while a 64-bit executable would only
need 16.  Yes, L1 & L2 caching would help some, but not if you are
moving huge amounts of data...

-- 
+------------------------------------------------------------+
| Ron Johnson, Jr.     mailto:ron.l.johnson@cox.net          |
| Jefferson, LA  USA   http://members.cox.net/ron.l.johnson  |
|                                                            |
| "Basically, I got on the plane with a bomb. Basically, I   |
|  tried to ignite it. Basically, yeah, I intended to damage |
|  the plane."                                               |
|    RICHARD REID, who tried to blow up American Airlines    |
|                  Flight 63                                 |
+------------------------------------------------------------+




view thread (10+ messages)  latest in thread

Message-ID: <1043056334.15592.167.camel@haggis>
Permalink:  ../1043056334.15592.167.camel@haggis/
Also on:    postgresql.org/message-id/1043056334.15592.167.camel@haggis

 · 

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 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-performance@postgresql.org
  Cc: ron.l.johnson@cox.net
  Subject: Re: x86-64 and PostgreSQL
  In-Reply-To: <1043056334.15592.167.camel@haggis>
  References: <1042867764.889.181.camel@haggis> <3E2BE4BF.28150.D33005A@localhost> <1043056334.15592.167.camel@haggis>

* 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