Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 2878B475D22 for ; Mon, 20 Jan 2003 04:59:22 -0500 (EST) Received: from www.pspl.co.in (www.pspl.co.in [202.54.11.65]) by postgresql.org (Postfix) with ESMTP id 4B878475CED for ; Mon, 20 Jan 2003 04:59:20 -0500 (EST) Received: (from root@localhost) by www.pspl.co.in (8.11.6/8.11.6) id h0K9xLJ27009 for ; Mon, 20 Jan 2003 15:29:21 +0530 Received: from daithan (daithan.intranet.pspl.co.in [192.168.7.161]) by www.pspl.co.in (8.11.6/8.11.0) with ESMTP id h0K9xKn27004 for ; Mon, 20 Jan 2003 15:29:20 +0530 From: "Shridhar Daithankar" To: PgSQL Performance ML Date: Mon, 20 Jan 2003 15:29:42 +0530 MIME-Version: 1.0 Subject: Re: x86-64 and PostgreSQL Reply-To: shridhar_daithankar@persistent.co.in Message-ID: <3E2C15E6.9191.DF2FEFC@localhost> References: <3E2BE4BF.28150.D33005A@localhost> In-reply-to: <1043056334.15592.167.camel@haggis> X-mailer: Pegasus Mail for Windows (v4.02) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/205 X-Sequence-Number: 852 On 20 Jan 2003 at 3:52, Ron Johnson wrote: > On Mon, 2003-01-20 at 00:29, Shridhar Daithankar wrote: > > 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... Well, that wasn't intended application aera of that remark. I was more on the line of, I have 16GB data of double precision which I need to shuffle thr. once in a while, should I use 32 bit or 64 bit? Something like that.. bit more macroscopic. I work on an application which is 32 bit on HP-UX 64 bit. It handles more than 15GB of data at some sites pretty gracefully..No need to move to 64 bit as yet.. Bye Shridhar -- Kramer's Law: You can never tell which way the train went by looking at the tracks.