| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>,Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Improving connection scalability: GetSnapshotData() |
| Date: | 2020-03-29 18:50:10 |
| Message-ID: | F0E7D264-FEA3-47D3-815E-C834569EBCDA@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On March 29, 2020 11:24:32 AM PDT, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> wrote:
> clearly a big win on majority
>of workloads, I think we still need to investigate different workloads
>on different hardware to ensure there is no regression.
Definitely. Which workloads are you thinking of? I can think of those affected facets: snapshot speed, commit speed with writes, connection establishment, prepared transaction speed. All in the small and large connection count cases.
I did measurements on all of those but prepared xacts, fwiw. That definitely needs to be measured, due to the locking changes around procarrayaddd/remove.
I don't think regressions besides perhaps 2pc are likely - there's nothing really getting more expensive but procarray add/remove.
Andres
Regards,
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2020-03-29 19:02:33 | Re: GSoC Proposal |
| Previous Message | Alexander Korotkov | 2020-03-29 18:24:32 | Re: Improving connection scalability: GetSnapshotData() |