Hash tables with finite buckets are less resistant to deletions

Yossi Kanizo*, David Hay, Isaac Keslassy

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

3 Scopus citations

Abstract

We show that when memory is bounded, i.e. memory buckets are finite, dynamic hash tables that allow insertions and deletions behave significantly worse than their static counterparts that only allow insertions. This behavior differs from previous results in which, when memory is unbounded, the two models behave similarly. We show the decrease in performance in dynamic hash tables using several hash-table schemes. We also provide tight upper and lower bounds on the achievable overflow fractions in these schemes. Finally, we propose an architecture with content-addressable memory (CAM), which mitigates this decrease in performance.

Original languageEnglish
Pages (from-to)1376-1389
Number of pages14
JournalComputer Networks
Volume56
Issue number4
DOIs
StatePublished - 16 Mar 2012

Bibliographical note

Funding Information:
Isaac Keslassy received the M.S. and Ph.D. degrees in electrical engineering from Stanford University, Stanford, CA, in 2000 and 2004, respectively. He is currently an associate professor in the electrical engineering department of the Technion, Haifa, Israel. His recent research interests include the design and analysis of high-performance routers and on-chip networks. He is the recipient of the Yigal Alon Fellowship, the ATS-WD Career Development Chair and the ERC Starting Grant.

Funding Information:
The work was partly supported by the European Research Council Starting Grant No. 210389 , the European Research Council Starting Grant No. 259085 , the Alon Fellowship, the ATS-WD Career Development Chair, and the Loewengart Research Fund .

Keywords

  • Dynamic hash tables
  • High-Speed networks
  • Queuing theory and analysis

Fingerprint

Dive into the research topics of 'Hash tables with finite buckets are less resistant to deletions'. Together they form a unique fingerprint.

Cite this