Re: BufferAlloc: don't take two simultaneous locks
От | Yura Sokolov |
---|---|
Тема | Re: BufferAlloc: don't take two simultaneous locks |
Дата | |
Msg-id | a9a81ddd10abde95196dba1892ee22c1606bcddc.camel@postgrespro.ru обсуждение исходный текст |
Ответ на | Re: BufferAlloc: don't take two simultaneous locks (Yura Sokolov <y.sokolov@postgrespro.ru>) |
Список | pgsql-hackers |
В Вт, 15/03/2022 в 13:47 +0300, Yura Sokolov пишет: > В Вт, 15/03/2022 в 16:25 +0900, Kyotaro Horiguchi пишет: > > > I lost access to Xeon 8354H, so returned to old Xeon X5675. > > ... > > > Strange thing: both master and patched version has higher > > > peak tps at X5676 at medium connections (17 or 27 clients) > > > than in first october version [1]. But lower tps at higher > > > connections number (>= 191 clients). > > > I'll try to bisect on master this unfortunate change. > > > > The reversing of the preference order between freshly-allocation and > > borrow-from-another-freelist might affect. > > `master` changed its behaviour as well. > It is not problem of the patch at all. Looks like there is no issue: old commmit 2d44dee0281a1abf behaves similar to new one at the moment. I think, something changed in environment. I remember there were maintanance downtime in the autumn. Perhaps kernel were updated or some sysctl tuning changed. ---- regards Yura.
В списке pgsql-hackers по дате отправления: