From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | mark(at)mark(dot)mielke(dot)cc |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Faster StrNCpy |
Date: | 2006-09-29 21:34:30 |
Message-ID: | 3776.1159565670@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
mark(at)mark(dot)mielke(dot)cc writes:
> If anybody is curious, here are my numbers for an AMD X2 3800+:
You did not show your C code, so no one else can reproduce the test on
other hardware. However, it looks like your compiler has unrolled the
memcpy into straight-line 8-byte moves, which makes it pretty hard for
anything operating byte-wise to compete, and is a bit dubious for the
general case anyway (since it requires assuming that the size and
alignment are known at compile time).
This does make me wonder about whether we shouldn't try the
strlen+memcpy implementation I proposed earlier ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-09-29 21:41:35 | Re: Per-database search_path |
Previous Message | mark | 2006-09-29 21:23:31 | Re: Faster StrNCpy |
From | Date | Subject | |
---|---|---|---|
Next Message | mark | 2006-09-29 21:59:17 | Re: Faster StrNCpy |
Previous Message | mark | 2006-09-29 21:23:31 | Re: Faster StrNCpy |