Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming.threads > #2745
| From | Ramine <ramine@1.1> |
|---|---|
| Newsgroups | comp.programming.threads |
| Subject | I have just read the following about Intel TSX |
| Date | 2014-12-06 17:04 -0800 |
| Organization | A noiseless patient Spider |
| Message-ID | <m5vufu$uk6$2@dont-email.me> (permalink) |
Hello, I have just read the following about Intel TSX: "At the moment, TSX is quite slow, even if there's no contention and you don't do anything in the block. There's a lot of overhead. Using TSX naively may slow down even threaded code. Getting significant performance gains from it is non-trivial." read more here a little bit down the webpage: http://cbloomrants.blogspot.ca/search?updated-min=2014-01-01T00:00:00-08:00&updated-max=2015-01-01T00:00:00-08:00&max-results=43 So i think my newer scalable distributed sequential lock is faster than Intel TSX on read-mostly scenarios, also my newer algorithm is kind of general synchronization mechanism because it works with both memory and hardisk. Thank you, Amine Moulay Ramdane.
Back to comp.programming.threads | Previous | Next — Next in thread | Find similar | Unroll thread
I have just read the following about Intel TSX Ramine <ramine@1.1> - 2014-12-06 17:04 -0800
Re: I have just read the following about Intel TSX "Chris M. Thomasson" <no@spam.invalid> - 2014-12-06 14:42 -0800
Re: I have just read the following about Intel TSX Melzzzzz <mel@zzzzz.com> - 2014-12-07 01:21 +0100
Re: I have just read the following about Intel TSX "Chris M. Thomasson" <no@spam.invalid> - 2014-12-06 16:31 -0800
csiph-web