From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org, dipiets(at)amazon(dot)com |
Subject: | Re: use a non-locking initial test in TAS_SPIN on AArch64 |
Date: | 2025-01-08 20:30:56 |
Message-ID: | Z37ggNnCZp-_gbNc@nathan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 08, 2025 at 03:23:45PM -0500, Tom Lane wrote:
> I just acquired an M4 Pro, which may also be too small to show any
> effect, but perhaps running the test there would at least give us
> more confidence that there's not a bad effect. Which test case(s)
> would you recommend trying?
Thanks! A select-only pgbench with many clients (I used 256 upthread) and
pg_stat_statements.track_planning enabled seems to be a pretty easy way to
stress spinlocks. The same test without track_planning enabled might also
be interesting. I'm looking for a way to stress LWLocks, too, and I will
share here when I either find an existing test or write something of my
own.
--
nathan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-01-08 20:35:38 | Re: improve DEBUG1 logging of parallel workers for CREATE INDEX? |
Previous Message | Jacob Champion | 2025-01-08 20:29:35 | Re: [PoC] Federated Authn/z with OAUTHBEARER |