Re: Fastest way to clone schema ~1000x

2024-02-29 Thread Emiel Mols
at 5:10 PM Adrian Klaver wrote: > On 2/26/24 01:06, Emiel Mols wrote: > > On Mon, Feb 26, 2024 at 3:50 PM Daniel Gustafsson > <mailto:dan...@yesql.se>> wrote: > > > > There is a measurable overhead in connections, regardless of if they > > are used &

Re: Fastest way to clone schema ~1000x

2024-02-26 Thread Emiel Mols
On Mon, Feb 26, 2024 at 3:50 PM Daniel Gustafsson wrote: > There is a measurable overhead in connections, regardless of if they are > used > or not. If you are looking to squeeze out performance then doing more over > already established connections, and reducing max_connections, is a good > pla

Re: Fastest way to clone schema ~1000x

2024-02-26 Thread Emiel Mols
2:14 PM Pavel Stehule wrote: > > > po 26. 2. 2024 v 8:08 odesílatel Emiel Mols napsal: > >> Thanks, as indicated we're using that right now. The 30% spinlock >> overhead unfortunately persists. >> > > try to increase shared_buffer > > 128MB ca

Re: Fastest way to clone schema ~1000x

2024-02-25 Thread Emiel Mols
s = 128MB log_line_prefix = '' synchronous_commit = 'off' wal_level = 'minimal' - linux perf report comparing schema-per-test vs database-per-test: https://ibb.co/CW5w2MW - Emiel On Mon, Feb 26, 2024 at 1:36 PM Pavel Stehule wrote: > Hi > > po 26. 2. 2024 v 7:28

Fastest way to clone schema ~1000x

2024-02-25 Thread Emiel Mols
Hello, To improve our unit and end-to-end testing performance, we are looking to optimize initialization of around 500-1000 database *schemas* from a schema.sql file. Background: in postgres, you cannot change databases on existing connections, and using schemas would allow us to minimize the amo