Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.programming.threads > #2758 > unrolled thread

More optimization of the reader-writer algorithms

Started byRamine <ramine@1.1>
First post2014-12-07 16:23 -0800
Last post2014-12-07 16:23 -0800
Articles 1 — 1 participant

Back to article view | Back to comp.programming.threads


Contents

  More optimization of the reader-writer algorithms Ramine <ramine@1.1> - 2014-12-07 16:23 -0800

#2758 — More optimization of the reader-writer algorithms

FromRamine <ramine@1.1>
Date2014-12-07 16:23 -0800
SubjectMore optimization of the reader-writer algorithms
Message-ID<m62gea$c6q$2@dont-email.me>
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.

[toc] | [standalone]


Back to top | Article view | comp.programming.threads


csiph-web