Re: BufferAlloc: don't take two simultaneous locks
| От | Ibrar Ahmed |
|---|---|
| Тема | Re: BufferAlloc: don't take two simultaneous locks |
| Дата | |
| Msg-id | CALtqXTdOUwZRLwh7Ua+EqncYa=UYBEKS1BBWmNPQLoqHfXhgmg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: BufferAlloc: don't take two simultaneous locks (Yura Sokolov <y.sokolov@postgrespro.ru>) |
| Ответы |
Re: BufferAlloc: don't take two simultaneous locks
|
| Список | pgsql-hackers |
On Tue, Jun 28, 2022 at 4:50 PM Yura Sokolov <y.sokolov@postgrespro.ru> wrote:
В Вт, 28/06/2022 в 14:26 +0300, Yura Sokolov пишет:
> В Вт, 28/06/2022 в 14:13 +0300, Yura Sokolov пишет:
>
> > Tests:
> > - tests done on 2 socket Xeon 5220 2.20GHz with turbo bust disabled
> > (ie max frequency is 2.20GHz)
>
> Forgot to mention:
> - this time it was Centos7.9.2009 (Core) with Linux mn10 3.10.0-1160.el7.x86_64
>
> Perhaps older kernel describes poor master's performance on 2 sockets
> compared to my previous results (when this server had Linux 5.10.103-1 Debian).
>
> Or there is degradation in PostgreSQL's master branch between.
> I'll try to check today.
No, old master commit ( 7e12256b47 Sat Mar 12 14:21:40 2022) behaves same.
So it is clearly old-kernel issue. Perhaps, futex was much slower than this
days.
The patch requires a rebase; please do that.
Hunk #1 FAILED at 231.
Hunk #2 succeeded at 409 (offset 82 lines).
1 out of 2 hunks FAILED -- saving rejects to file src/include/storage/buf_internals.h.rej
Ibrar Ahmed
В списке pgsql-hackers по дате отправления: