From: Josh Berkus <josh@agliodbs.com>
To: Adam Scott <adam.c.scott@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: Queries Per Second (QPS)
Date: Wed, 30 Sep 2015 10:06:46 -0700
Message-ID: <560C16A6.1000004@agliodbs.com> (raw)
In-Reply-To: <WM!fad2df3368f1aadefa9808a3b60ff6bc57b663bd27edb11b6b435ff8377baa929deed2b99bafde12024dc6c4e56fc5fe!@asav-3.01.com>
References: <CA+s62-ObrbjC8rXKvwE-u3XLYkJEcDLJsN=rkPCLNLhRew9QDg@mail.gmail.com>
<WM!fad2df3368f1aadefa9808a3b60ff6bc57b663bd27edb11b6b435ff8377baa929deed2b99bafde12024dc6c4e56fc5fe!@asav-3.01.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 09/26/2015 09:24 AM, Adam Scott wrote:
> How do we measure queries per second (QPS), not transactions per second,
> in PostgreSQL without turning on full logging which has a performance
> penalty and can soak up lots of disk space?
Measure it from the client side. pgBench does this.
If you mean on your production workload, then I recommend using a
connection proxy which counts statements. A few exist for Postgres, for
example:
VividCortex:
https://www.vividcortex.com/blog/2015/05/13/announcing-vividcortex-network-analyzer-mysql-postgresql...
WireShark: https://github.com/dalibo/pgshark
You'd need to measure how much one of these tools affects your QPS, of
course, but that should be easily measurable on a test system.
Also, if the PostgresQL activity log is moved to a seperate SSD from the
database storage, I've found overhead in writing to it to be less than
3% ... depending on the nature of your query traffic. Pathological
situations are mainly databases which have a high volume of very long
queries or failed connection attempts.
>
> We are using 8.4, but I'm interested in any version as well.
You are aware that 8.4 is EOL, yes? Not to mention missing 5 years of
performance improvements ...
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, adam.c.scott@gmail.com
Subject: Re: Queries Per Second (QPS)
In-Reply-To: <560C16A6.1000004@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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