Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming.threads > #1944
| From | aminer <aminer@toto.net> |
|---|---|
| Newsgroups | comp.programming.threads, comp.programming |
| Subject | Scalability and hashtables and databases |
| Date | 2013-10-21 17:29 -0700 |
| Organization | albasani.net |
| Message-ID | <l446bb$ds0$1@news.albasani.net> (permalink) |
Cross-posted to 2 groups.
Hello, I come to an interresting subject, i want to talk about the scalability on multicores of the parallel hashtables and databases engines... i am wondering how can you say that a parallel hashtable can scale on multicores if the random key acesses are cache unfreiendly and the parallel hashtable is memory bound ? i think since the parallel hashtable is memory bound and the random accesses are cache unfreindly that means that the parallel hashtable will not scale on multicores, when you are testing your parallel hashtable, you have also to test the cache misses on the data, cause i think that the data is part of the hashtable application, i mean the parallel hashtable concept is highly interconnected with the way that the data is accessed randomly in a cache unfreindly manner and the hashtables concept is is highly interconnected with the way the hashtable data is accessed in memory bound manner, so this why i say that parallel hashtables are not scalable on multicores, it's the same for database engines , since they are disk bound, so they are not scalable, and even if they are in-memory databases they will be memory bound and cache unfreindly, so databases are not scable either on mutilcores. Thank you, Amine Moulay Ramndane
Back to comp.programming.threads | Previous | Next — Next in thread | Find similar
Scalability and hashtables and databases aminer <aminer@toto.net> - 2013-10-21 17:29 -0700
Re: Scalability and hashtables and databases aminer <aminer@toto.net> - 2013-10-21 17:34 -0700
Re: Scalability and hashtables and databases "Chris M. Thomasson" <no@spam.invalid> - 2013-10-21 15:10 -0700
csiph-web