NAMEDATALEN's benchmarked are 32, 64, 128 and 512. Attached is the
shell script I used to do it.
First row of a set is the time(1) for the pgbench -i run, second is
the actual benchmark. Aside from the 'real' time of 64 there is a
distinct increase in time required, but not significant.
Benchmarks were run for 3000 transactions with scale factor of 5, but
only 1 client. If there is a preferred setting for pgbench I can do
an overnight run with it. Machine is a dual 500Mhz celery with 384MB
ram and 2 IBM Deskstars in Raid 0, and a seperate system drive.
Anything but 32 fails the 'name' check in the regression tests -- I
assume this is expected?
Don't know why 64 has a high 'real' time, but the system times are
appropriate.
NAMEDATALEN: 32
158.97 real 1.81 user 0.14 sys
80.58 real 1.30 user 3.81 sys
NAMEDATALEN: 64
248.40 real 1.85 user 0.10 sys
96.36 real 1.44 user 3.86 sys
NAMEDATALEN: 128
156.74 real 1.84 user 0.10 sys
94.36 real 1.47 user 4.01 sys
NAMEDATALEN: 512
157.99 real 1.83 user 0.12 sys
101.14 real 1.47 user 4.23 sys
--
Rod Taylor
Your eyes are weary from staring at the CRT. You feel sleepy. Notice
how restful it is to watch the cursor blink. Close your eyes. The
opinions stated above are yours. You cannot imagine why you ever felt
otherwise.
