From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pgbench: option delaying queries till connections establishment? |
Date: | 2020-03-01 21:16:06 |
Message-ID: | alpine.DEB.2.21.2003012113350.25187@pseudo |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello Andres,
> FWIW, leaving windows, error handling, and other annoyances aside, this
> can be implemented fairly simply. See below.
Attached an attempt at improving things.
I've put 2 barriers: one so that all threads are up, one when all
connections are setup and the bench is ready to go.
I've done a blind attempt at implementing the barrier stuff on windows.
I've changed the performance calculations depending on -C or not. Ramp-up
effects are smoothed.
I've merged all time-related stuff (time_t, instr_time, int64) to use a
unique type (pg_time_usec_t) and set of functions/macros, which simplifies
the code somehow.
I've tried to do some variable renaming to distinguish timestamps and
intervals.
This is work in progress.
--
Fabien.
Attachment | Content-Type | Size |
---|---|---|
pgbench-barrier-2.patch | text/x-diff | 30.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-03-01 21:16:59 | Re: Commitfest 2020-03 Now in Progress |
Previous Message | Tom Lane | 2020-03-01 21:13:57 | Re: Re[2]: bool_plperl transform |