In the last week, I focused on tuning the performance of skip list and fixed 
several bugs.
1. As only out-conflicts are checked in RWConflictExists, I removed all 
modification concerned with in-conflicts;
2. If the conflict list is too short, I inserted an item just like inserting 
into an ordered linked list, that is, 
comparing items existing in the list one by one to find the right position. 
Using skip list is slow when the list is short.
3. Not using the abstract skip list interface; I was afraid that it would bring 
a little overhead. But results showed that 
it had no influence. I will roll it back if necessary.

Sadly, The performance is not better than the original version.  But it's 
highest one among all efforts I did before.
It likes hash table. Tracking conflict is faster but inserting conflicts is 
In a quick test, cpu cycles consumed by two functions 
RWConflictExists/SetRWConflict is as below.
| | RWConflictExists | SetRWConflict |
| linked list | 1.39% | 0.14% |
| skip list | 1.15% | 0.35% |

According to the suggestions of Alvaro,  I'll give a detailed performance 
report tomorrow.



Mengxing Liu

Attachment: skip-list-for-conflict-tracking.patch
Description: Binary data

Sent via pgsql-hackers mailing list (
To make changes to your subscription:

Reply via email to