Robert Haas <robertmh...@gmail.com> writes:
> On machines with lots of CPU cores, pgbench can start eating up a lot
> of system time. Investigation reveals that the problem is with
> random(),
Interesting.
> I patched it to use random_r() - the patch is attached - and here are
> the (rather gratifying) results of that test:
> Since a client-limited benchmark isn't very interesting, I think this
> change makes sense. Thoughts? Objections?
Portability, or rather lack of it. What about using erand48, which we
already have a dependency on (and substitute code for)?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
