LwLockRelease performance

Поиск
Список
Период
Сортировка
От Ashkil Dighin
Тема LwLockRelease performance
Дата
Msg-id CAH6zzqCqZGqwDBWQqHb=XSVMyRBHBE+bh5sVnrQe-UE0uabwtg@mail.gmail.com
обсуждение исходный текст
Ответы Re: LwLockRelease performance  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: LwLockRelease performance  (Andres Freund <andres@anarazel.de>)
Список pgsql-performance
Hi 
The performance bottleneck in LWLockRelease()method goes through an array one by one to see which lock was released with O(N). As soon as the lock is found it performs an array to remove the lock.
As linear search and compaction delays the release of the lock forcing the other Postgres instances WAiting for the lock to be released 
Is any possible solution like 
1. LWLockRelease() releases the lock first and then remove held lock from the array
2. Binary search (like non-linear structure) to reduce on high searching and remove all held locks 

В списке pgsql-performance по дате отправления:

Предыдущее
От: pgsql-performance@jhacker.de
Дата:
Сообщение: pg_trgm word_similarity query does not use index for input strings longer than 8 characters
Следующее
От: Tom Lane
Дата:
Сообщение: Re: LwLockRelease performance