pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedbenchmarking proposed config
4+ messages / 4 participants
[nested] [flat]
* benchmarking proposed config
@ 2020-02-20 16:12 Scott Ribe <scott_ribe@killerbytes.com>
0 siblings, 2 replies; 4+ messages in thread
From: Scott Ribe @ 2020-02-20 16:12 UTC (permalink / raw)
To: pgsql-admin
Does anyone have suggestions for a utility that would easily let us mirror all queries to a "shadow" PG cluster, so that we can compare performance of our current production config against a new proposed config with our actual production traffic?
(We could live with the new one falling behind as long as queries were queued not lost--in fact we know this will happen.)
--
Scott Ribe
scott_ribe@elevated-dev.com
https://www.linkedin.com/in/scottribe/
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: benchmarking proposed config
@ 2020-02-21 09:55 Jakub Olczyk <jwo@disroot.org>
parent: Scott Ribe <scott_ribe@killerbytes.com>
1 sibling, 1 reply; 4+ messages in thread
From: Jakub Olczyk @ 2020-02-21 09:55 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Hi Scott,
On Thu, 20 Feb 2020 09:12:09 -0700
Scott Ribe <scott_ribe@killerbytes.com> wrote:
> Does anyone have suggestions for a utility that would easily let us
> mirror all queries to a "shadow" PG cluster, so that we can compare
> performance of our current production config against a new proposed
> config with our actual production traffic?
I am not sure if this would be an acceptable solution for you but there
is an open source utility called pgreplay[1]. Here is the description:
> pgreplay reads a PostgreSQL log file (*not* a WAL file), extracts the
> SQL statements and executes them in the same order and relative time
> against a PostgreSQL database cluster.
This of course means that you'd need to have a fairly "chatty" log
configuration, but maybe it could work for your needs?
Cheers,
jwo
[1]: https://github.com/laurenz/pgreplay
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: benchmarking proposed config
@ 2020-02-21 14:53 Scott Ribe <scott_ribe@elevated-dev.com>
parent: Jakub Olczyk <jwo@disroot.org>
0 siblings, 0 replies; 4+ messages in thread
From: Scott Ribe @ 2020-02-21 14:53 UTC (permalink / raw)
To: Jakub Olczyk <jwo@disroot.org>; +Cc: pgsql-admin@lists.postgresql.org
On Feb 21, 2020, at 2:55 AM, Jakub Olczyk <jwo@disroot.org> wrote:
>
> This of course means that you'd need to have a fairly "chatty" log
> configuration, but maybe it could work for your needs?
It sure might work; we'll give it a try--hopefully we can log all SQL without filling disk or undue performance hit, we'll see.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: benchmarking proposed config
@ 2020-02-24 17:15 bricklen <bricklen@gmail.com>
parent: Scott Ribe <scott_ribe@killerbytes.com>
1 sibling, 0 replies; 4+ messages in thread
From: bricklen @ 2020-02-24 17:15 UTC (permalink / raw)
To: Scott Ribe <scott_ribe@killerbytes.com>; +Cc: pgsql-admin
On Thu, Feb 20, 2020 at 12:10 PM Scott Ribe <scott_ribe@killerbytes.com>
wrote:
> Does anyone have suggestions for a utility that would easily let us mirror
> all queries to a "shadow" PG cluster, so that we can compare performance of
> our current production config against a new proposed config with our actual
> production traffic?
>
> (We could live with the new one falling behind as long as queries were
> queued not lost--in fact we know this will happen.)
>
PgShark might work for this
https://github.com/dalibo/pgshark
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2020-02-24 17:15 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-02-20 16:12 benchmarking proposed config Scott Ribe <scott_ribe@killerbytes.com>
2020-02-21 09:55 ` Jakub Olczyk <jwo@disroot.org>
2020-02-21 14:53 ` Scott Ribe <scott_ribe@elevated-dev.com>
2020-02-24 17:15 ` bricklen <bricklen@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox