From: | Erik Wienhold <ewie(at)ewie(dot)name> |
---|---|
To: | Richard Brockie <richard(dot)brockie(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Slow down dev database transactions/second for testing? |
Date: | 2023-02-05 23:05:29 |
Message-ID: | 1186356122.107942.1675638329216@office.mailbox.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On 05/02/2023 23:17 CET Richard Brockie <richard(dot)brockie(at)gmail(dot)com> wrote:
>
> I maintain a Django webapp that uses postgresql and can create inefficient
> queries if I'm not careful. I'm looking for ways to mimic a congested db
> server in development to expose these queries.
pgbench is what your looking for: https://www.postgresql.org/docs/current/pgbench.html
You can run custom statements with the --file option. Get the statements that
Django generates and let pgbench run those to analyze the bottlenecks. Or let
pgbench create load for some time (see option --time) while you debug your
Django app.
> The configuration of postgresql is complicated - is there a simple method by
> which I could, for example limit the number of transactions/second to a
> certain level by adjusting postgresql.conf?
No. Postgres will execute as fast as possible with the available resources.
--
Erik
From | Date | Subject | |
---|---|---|---|
Next Message | Dionisis Kontominas | 2023-02-05 23:08:28 | Question regarding UTF-8 data and "C" collation on definition of field of table |
Previous Message | Richard Brockie | 2023-02-05 22:17:13 | Slow down dev database transactions/second for testing? |