of postgres.
-rocco
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bruce Momjian
Sent: Wednesday, February 01, 2006 12:11 PM
To: Seneca Cunningham
Cc: Martijn van Oosterhout; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Some platform
] On Behalf Of Bruce Momjian
Sent: Wednesday, February 01, 2006 12:11 PM
To: Seneca Cunningham
Cc: Martijn van Oosterhout; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Some platform-specific MemSet research
My guess is that there is some really fast assembler for
memory copy
My guess is that there is some really fast assembler for memory copy on
AIX, and only libc memset() has it. If you want, we can make
MEMSET_LOOP_LIMIT in c.h a configure value, and allow template/aix to
set it to zero, causing memset() to be always used.
Are you prepared to make this
Martijn van Oosterhout wrote:
On Tue, Jan 24, 2006 at 05:24:28PM -0500, Seneca Cunningham wrote:
After reading the post on -patches proposing that MemSet be changed to
use long instead of int32 on the grounds that a pair of x86-64 linux
boxes took less time to execute the long code 64*10^6
After reading the post on -patches proposing that MemSet be changed to
use long instead of int32 on the grounds that a pair of x86-64 linux
boxes took less time to execute the long code 64*10^6 times[1], I took a
look at how the testcode performed on AIX with gcc. While the switch to
long did
On Tue, Jan 24, 2006 at 05:24:28PM -0500, Seneca Cunningham wrote:
After reading the post on -patches proposing that MemSet be changed to
use long instead of int32 on the grounds that a pair of x86-64 linux
boxes took less time to execute the long code 64*10^6 times[1], I took a
look at how
