Ramine
12/8/2014 12:23:00 AM
Hello,
If you want to implement an in-memory database with
my scalable distributed sequential lock, and you want
to optimize more the writer side, i mean if you want to
eliminate the expensive full memory barrier of the lock on the writer
side , what can you do about it ? you can use for example a client
server mechanism , that means the data is put by the producer threads on
a queue , and the consumer thread will execute alone the
writer section, and this way you can delete the lock from
the writer side, this will make the writer section much much
faster.
Thank you,
Amine Moulay Ramdane.