Re: Patch: fix lock contention for HASHHDR.mutex
| От | Aleksander Alekseev |
|---|---|
| Тема | Re: Patch: fix lock contention for HASHHDR.mutex |
| Дата | |
| Msg-id | 20151211204219.273b3acb@fujitsu обсуждение исходный текст |
| Ответ на | Re: Patch: fix lock contention for HASHHDR.mutex (Aleksander Alekseev <a.alekseev@postgrespro.ru>) |
| Список | pgsql-hackers |
Oops. s/approve or disapprove/confirm or deny/ On Fri, 11 Dec 2015 19:14:41 +0300 Aleksander Alekseev <a.alekseev@postgrespro.ru> wrote: > Hello, Tom > > I see your point, but I would like to clarify a few things. > > 1. Do we consider described measurement method good enough to conclude > that sometimes PostgreSQL really spends 3 ms in a spinlock (like a RTT > between two Internet hosts in the same city)? If not, what method > should be used to approve or disapprove this? > > 2. If we agree that PostgreSQL does sometimes spend 3 ms in a spinlock > do we consider this a problem? > > 3. If we consider this a problem, what method is considered > appropriate to find a real reason of such behaviour so we could fix > it? > > Best regards, > Aleksander > >
В списке pgsql-hackers по дате отправления: