- An important subject - 1 Update
- cmsg cancel <mg70ba$oe8$2@dont-email.me> - 1 Update
| Ramine <ramine@1.1>: Apr 09 07:09PM -0700 Hello, I have come to a very important subject... As you have noticed i have implemented a concurrent Skiplist, here it is: https://sites.google.com/site/aminer68/concurrent-skiplist As you will notice this concurrent Skiplist uses a distributed reader-writer lock , but what is special about this concurrent Skiplist? if you look at the other scalable concurrent Skiplists that are lockfree or that uses locks, you will immediatly notice that they write and read there contents BY VALUE , and this is a serious limitation, because if you want to insert complex objects BY REFERENCE and work with them like a database, this is not possible, this is not the same as my concurrent Skiplist above, because my concurrent Skiplist above works by inserting the object by reference and this is really useful , other than that my concurrent Skiplist have a decent throughput on the writer side and it is scalable on the reader side, other than that it has also another advantage because it facilitates a lot the reasonning about correctness and that's also very important. Thank you, Amine Moulay Ramdane. |
| bleachbot <bleachbot@httrack.com>: Apr 10 01:01AM +0200 |
| You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to comp.programming.threads+unsubscribe@googlegroups.com. |
No comments:
Post a Comment