On Tue, Mar 18, 2025 at 5:04 PM Andres Freund wrote:
> Is that actually a good description of what we assume? I don't know where
> that
> 90% is coming from?
That one's all my fault. It was an attempt to curve-fit backwards why the
4.0 number Tom set with his initial commit worked as well as i
On Thu, Nov 14, 2024 at 5:41 PM Noah Misch wrote:
> I'm hearing the only confirmed impact on non-assert builds is the need to
> recompile timescaledb. (It's unknown whether recompiling will suffice for
> timescaledb. For assert builds, six PGXN extensions need recompilation.)
>
That matches wh
On Fri, Jun 9, 2023 at 1:25 PM Gurjeet Singh wrote:
> > $ pgbench -i -I dtGvp -s 500
>
> The steps are severely under-documented in pgbench --help output.
>
I agree it's not easy to find information. I just went through double
checking I had the order recently enough to remember what I did.
On Thu, Jun 8, 2023 at 11:40 AM Tomas Vondra
wrote:
> We already do prefetching for bitmap index scans, where the bitmap heap
> scan prefetches future pages based on effective_io_concurrency. I'm not
> sure why exactly was prefetching implemented only for bitmap scans
At the point Greg Stark wa
On Tue, May 23, 2023 at 1:33 PM Tristan Partin wrote:
> We (Neon) have noticed that pgbench can be quite slow to populate data
> in regard to higher latency connections. Higher scale factors exacerbate
> this problem. Some employees work on a different continent than the
> databases they might be
On Fri, Jun 9, 2023 at 4:06 AM Gurjeet Singh wrote:
> There is no mention of perf or similar utilities in pgbench-tools
> docs. I'm guessing Linux is the primary platform pgbench-tools gets
> used on most. If so, I think it'd be useful to mention these tools and
> snippets in there to make others
Let me start with the happy ending to this thread:
$ pgbench -S -T 10 -c 32 -j 32 -M prepared -P 1 pgbench
pgbench (15.3 (Ubuntu 15.3-1.pgdg23.04+1))
progress: 1.0 s, 1015713.0 tps, lat 0.031 ms stddev 0.007, 0 failed
progress: 2.0 s, 1083780.4 tps, lat 0.029 ms stddev 0.007, 0 failed...
progress:
On Thu, Jun 8, 2023 at 6:18 PM Andres Freund wrote:
> Could you get a profile with call graphs? We need to know what leads to all
> those osq_lock calls.
> perf record --call-graph dwarf -a sleep 1
> or such should do the trick, if run while the workload is running.
>
I'm doing something wrong b
Attached is a combined diff for a set of related patches to the built-in
pgbench workloads. One commit adds an INSERT workload. One fixes the long
standing 0 length filler issue. A new --extra-indexes option adds the
indexes needed for lookups added by the --foreign-keys option.
The commits are
On Wed, Jun 16, 2021 at 2:59 PM Fabien COELHO wrote:
> I'm unhappy because I already added tap tests for time-sensitive features
> (-T and others, maybe logging aggregates, cannot remember), which have
> been removed because they could fail under some circonstances (eg very
> very very very slow
Back on March 10 Thomas Munro committed and wrestled multiple reworks of
the pgbench code from Fabien and the crew. The feature to synchronize
startup I'm looking forward to testing now that I have a packaged beta.
Variations on that problem have bit me so many times I added code last year
to my p
11 matches
Mail list logo
