Re: Lock contention high
От | Andres Freund |
---|---|
Тема | Re: Lock contention high |
Дата | |
Msg-id | 2A5AB443-64E5-42DC-936A-C521ADD6B1BD@anarazel.de обсуждение исходный текст |
Ответ на | Lock contention high (Ashkil Dighin <ashkildighin76@gmail.com>) |
Ответы |
Re: Lock contention high
|
Список | pgsql-performance |
Hi, On October 27, 2021 2:44:56 PM PDT, Ashkil Dighin <ashkildighin76@gmail.com> wrote: >Hi, >Yes, lock contention reduced with postgresqlv14. >Lock acquire reduced 18% to 10% >10.49 %postgres postgres [.] LWLockAcquire >5.09% postgres postgres [.] _bt_compare > >Is lock contention can be reduced to 0-3%? Probably not, or at least not easily. Because of the atomic instructions the locking also includes some other costs (e.g.cache misses, serializing store buffers,...). There's a good bit we can do to increase the cache efficiency around buffer headers, but it won't get us quite that low I'dguess. >On pg-stat-activity shown LwLock as “BufferCounter” and “WalInsert” Without knowing what proportion they have to each and to non-waiting backends that unfortunately doesn't help that much.. Andres -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
В списке pgsql-performance по дате отправления: