From: | Pailloncy Jean-Gerard <jg(at)rilk(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Concurrent free-lock |
Date: | 2005-01-25 09:25:08 |
Message-ID: | 01543598-6EB3-11D9-8B82-000A95DE2550@rilk.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Here is some pretty good info on lock-free structures... I'm pretty
> sure I tested their code in a multithreaded high-concurrency
> environment and experienced the problems I was discussing.
I understand.
The algorithm is quite complex.
The old version was not really fast.
In the paper cited, some tests was done with 90 concurrent threads, and
with different density of data inside the structure. I found really
interresting (but I am not expert of this field).
Most of the researcher that work on "concurrent lock free" algorithm
understand the complexity, and to help anyone to use it, they provide
this technology for a whole algorithm.
There are libraries for red-black tree, skip-list, hash-table, etc.
I did not read the detail of the code to know if we may use it as a
direct remplacement.
http://www.cl.cam.ac.uk/Research/SRG/netos/lock-free/
http://www.cl.cam.ac.uk/users/kaf24/lockfree.html
http://www.audiomulch.com/~rossb/code/lockfree/
http://www.cs.rochester.edu/u/scott/synchronization/
Cordialement,
Jean-Gérard Pailloncy
From | Date | Subject | |
---|---|---|---|
Next Message | Bojidar Mihajlov | 2005-01-25 09:27:07 | RQ: Prepared statements used by multiple connections |
Previous Message | ITAGAKI Takahiro | 2005-01-25 09:06:23 | WAL: O_DIRECT and multipage-writer |