Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming.threads > #2760
| From | Ramine <ramine@1.1> |
|---|---|
| Newsgroups | comp.programming.threads |
| Subject | Re: More about scalability |
| Date | 2014-12-07 17:10 -0800 |
| Organization | A noiseless patient Spider |
| Message-ID | <m62j71$mph$1@dont-email.me> (permalink) |
| References | <m62hae$g4b$2@dont-email.me> |
Hello, But you have to use this optimization: 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.
Back to comp.programming.threads | Previous | Next — Previous in thread | Find similar | Unroll thread
More about scalability Ramine <ramine@1.1> - 2014-12-07 16:38 -0800 Re: More about scalability Ramine <ramine@1.1> - 2014-12-07 17:10 -0800
csiph-web