Re: [SR-Users] HTable 'size' parameter

2010-10-21 Thread Elena-Ramona Modroiu
Maybe the term entry should be replaced with slot, looks to be more standard. A good doc about hash tables is on wikipedia: http://en.wikipedia.org/wiki/Hash_table The htable module keeps the number of items in a slot, but not exported via rpc, this could be added in the future. Ramona On

Re: [SR-Users] HTable 'size' parameter

2010-10-17 Thread Iñaki Baz Castillo
2010/10/16 Uriel Rozenbaum uriel.rozenb...@gmail.com: What would be best to optimize the system is to have some statistic information, save every now and then the status of the htable and act accordingly to: - If the table is pretty much or completely used and you have collisions, make the

Re: [SR-Users] HTable 'size' parameter

2010-10-16 Thread Uriel Rozenbaum
Iñaki, Just as an addition from experience on hash tables, the first sweet-spot on the design is to have a fairly good algorithm so that different keys are mapped on different hash values. You cannot pick this (as far as I read) but we'll think it as fair enough. What you can do to help the

Re: [SR-Users] HTable 'size' parameter

2010-10-16 Thread Juha Heinanen
Uriel Rozenbaum writes: What would be best to optimize the system is to have some statistic information, save every now and then the status of the htable and act accordingly to: it would indeed be nice of htable module would exports stats about collisions. -- juha

Re: [SR-Users] HTable 'size' parameter

2010-10-16 Thread Alex Balashov
On 10/16/2010 09:18 AM, Juha Heinanen wrote: Uriel Rozenbaum writes: What would be best to optimize the system is to have some statistic information, save every now and then the status of the htable and act accordingly to: it would indeed be nice of htable module would exports stats about