Prefix Hash Tree an Indexing Data Structure Over Distributed Hash

Total Page:16

File Type:pdf, Size:1020Kb

Prefix Hash Tree an Indexing Data Structure Over Distributed Hash Prefix Hash Tree An Indexing Data Structure over Distributed Hash Tables Sriram Ramabhadran ∗ Sylvia Ratnasamy University of California, San Diego Intel Research, Berkeley Joseph M. Hellerstein Scott Shenker University of California, Berkeley International Comp. Science Institute, Berkeley and and Intel Research, Berkeley University of California, Berkeley ABSTRACT this lookup interface has allowed a wide variety of Distributed Hash Tables are scalable, robust, and system to be built on top DHTs, including file sys- self-organizing peer-to-peer systems that support tems [9, 27], indirection services [30], event notifi- exact match lookups. This paper describes the de- cation [6], content distribution networks [10] and sign and implementation of a Prefix Hash Tree - many others. a distributed data structure that enables more so- phisticated queries over a DHT. The Prefix Hash DHTs were designed in the Internet style: scala- Tree uses the lookup interface of a DHT to con- bility and ease of deployment triumph over strict struct a trie-based structure that is both efficient semantics. In particular, DHTs are self-organizing, (updates are doubly logarithmic in the size of the requiring no centralized authority or manual con- domain being indexed), and resilient (the failure figuration. They are robust against node failures of any given node in the Prefix Hash Tree does and easily accommodate new nodes. Most impor- not affect the availability of data stored at other tantly, they are scalable in the sense that both la- nodes). tency (in terms of the number of hops per lookup) and the local state required typically grow loga- Categories and Subject Descriptors rithmically in the number of nodes; this is crucial since many of the envisioned scenarios for DHTs C.2.4 [Comp. Communication Networks]: Dis- involve extremely large systems (such as P2P mu- tributed Systems|distributed applications; E.1 [Data sic file sharing). However, DHTs, like the Internet, Structures]: distributed data structures; H.3.1 [Info- deliver "best-effort” semantics; put's and get's are rmation Storage and Retrieval]: Content Anal- likely to succeed, but the system provides no guar- ysis and Indexing|indexing methods antees. As observed by others [36, 5], this conflict between scalability and strict semantics appears General Terms to be inevitable and, for many large-scale Inter- Algorithms, Design, Performance net systems, the former is deemed more important than the latter. Keywords While DHTs have enjoyed some success as a build- distributed hash tables, data structures, range queries ing block for Internet-scale applications, they are seriously deficient in one regard: they only directly 1. INTRODUCTION support exact match queries. Keyword queries can The explosive growth but primitive design of peer- be derived from these exact match queries in a to-peer file-sharing applications such as Gnutella straightforward but inefficient manner; see [25, 20] [7] and KaZaa [29] inspired the research community for applications of this to DHTs. Equality joins to invent Distributed Hash Tables (DHTs) [31, 24, can also be supported within a DHT framework; see [15]. However, range queries, asking for all ob- 14, 26, 22, 23]. Using a structured overlay network, jects with values in a certain range, are particularly DHTs map a given key to the node in the network difficult to implement in DHTs. This is because holding the object associated with that key; this DHTs use hashing to distribute keys uniformly and lookup operation lookup(key) can be used to sup- so can't rely on any structural properties of the key port the canonical put(key,value) and get(key) space, such as an ordering among keys. hash table operations. The broad applicability of ∗email [email protected] Range queries arise quite naturally in a number of Leaf nodes Keys 000* 000001 0 0 1 000100 000100 00100* 001001 1 001010* 001010 0 1 0 1 001010 001010 2 001011* 001011 0 1 0 1 001011 0011* 01* 010000 3 010101 0 1 10* 100010 101011 4 101111 0 1 110* 110000 110010 5 110011 0 1 110110 111* 111000 111010 6 Figure 1: Prefix Hash Tree potential application domains: against data loss when nodes go down1, the failure of any given node in the Prefix Hash Tree does not Databases Peer-to-peer databases [15] need to sup- affect the availability of data stored at other nodes. port SQL-type relational queries in a distributed fashion. Range predicates are a key component in But perhaps the most crucial property of PHT is SQL. that it is built entirely on top of the lookup inter- face, and thus can run over any DHT. That is, PHT Distributed computing Resource discovery requires uses only the lookup(key) operation common to locating resources within certain size ranges in a all DHTs and does not, as in SkipGraph [1] and decentralized manner. other such approaches, assume knowledge of nor require changes to the DHT topology or routing Location-aware computing Many applications want behavior. While designs that rely on such lower- to locate nearby resources (computing, human or layer knowledge and modifications are appropriate commercial) based on a user's current location, for contexts where the DHT is expressly deployed which is essentially a 2-dimensional range query for the purpose of supporting range queries, we ad- based on geographic coordinates. dress the case where one must use a pre-existing DHT. This is particularly important if one wants Scientific computing Parallel N-body computations to make use of publicly available DHT services, [34] require 3-dimensional range queries for accu- such as OpenHash [18]. rate approximations. The remainder of the paper is organized as fol- In this paper, we address the problem of efficiently lows. Section 2 describes the design of the PHT supporting 1-dimensional range queries over a DHT. data structure. Section 3 presents the results of an Our main contribution is a novel trie-based dis- experimental evaluation. Section 4 surveys related tributed data structure called Prefix Hash Tree (hence- work and section 5 concludes. forth abbreviated as PHT) that supports such queries. As a corollary, the PHT can also support heap queries (\what is the maximum/minimum ?"), prox- 2. DATA STRUCTURE This section describes the PHT data structure, along imity queries (\what is the nearest element to X with related algorithms. ?"), and, in a limited way, multi-dimensional ana- logues of the above, thereby greatly expanding the querying facilities of DHTs. PHT is efficient, in 2.1 PHT Description that updates are doubly logarithmic in the size For the sake of simplicity, it is assumed that the do- of the domain being indexed. Moreover, PHT is main being indexed is f0; 1gD, i.e., binary strings self-organizing and load-balanced. PHT also toler- ates failures well; while it cannot by itself protect 1But PHT can take advantage of any replication or other data-preserving technique employed by a DHT. of length D, although the discussion extends nat- in regions of the domain which are sparsely popu- urally to other domains. Therefore, the data set lated. Finally, property 5 ensures that the leaves indexed by the PHT consists of some number N of of the PHT form a doubly linked list, which en- D-bit binary keys. ables sequential traversal of the leaves for answer- ing range queries. In essence, the PHT data structure is a binary trie built over the data set. Each node of the trie is As described this far, the PHT structure is a fairly labeled with a prefix that is defined recursively: routine binary trie. The novelty of PHT lies in given a node with label l, its left and right child how this logical trie is distributed among the peers nodes are labeled l0 and l1 respectively. The root in the network; i.e., in how PHT vertices are as- is labeled with the attribute being indexed, and signed to DHT nodes. This is achieved by hashing downstream nodes are labeled as above. the prefix labels of PHT nodes over the DHT iden- tifier space. A node with label l is thus assigned The following properties are invariant in a PHT. 4 to the peer to which l is mapped by the DHT, i.e., the peer whose identifier is closest to HASH(l). 1. (Universal prefix) Each node has either 0 or 2 This hash-based assignment implies that given a la- children. bel, it is possible to locate its corresponding PHT node via a single DHT lookup. This \direct access" 2. (Key storage) A key K is stored at a leaf node property is unlike the successive link traversals as- whose label is a prefix of K. sociated with typical data structures and results in the PHT having several desirable features that are 3. (Split) Each leaf node stores atmost B keys. discussed subsequently. 4. (Merge) Each internal node contains atleast 2.2 PHT Operations (B + 1) keys in its sub-tree. This section describes algorithms for PHT opera- tions. 5. (Threaded leaves) Each leaf node maintains a pointer to the leaf nodes on its immediate left and and immediate right respectively.2 2.2.1 Lookup Given a key K, a PHT lookup operation returns Property 1 guarantees that the leaf nodes of the the unique leaf node leaf(K) whose label is a prefix PHT form a universal prefix set 3. Consequently, of K. Because there are (D + 1) distinct prefixes given any key K 2 f0; 1gD , there is exactly one leaf of K, there are (D + 1) potential candidates; an obvious algorithm is to perform a linear scan of node leaf(K) whose label is a prefix of K. Prop- these (D + 1) nodes until the required leaf node is erty 2 states that the key K is stored at leaf(K).
Recommended publications
  • Binary Search Tree
    ADT Binary Search Tree! Ellen Walker! CPSC 201 Data Structures! Hiram College! Binary Search Tree! •" Value-based storage of information! –" Data is stored in order! –" Data can be retrieved by value efficiently! •" Is a binary tree! –" Everything in left subtree is < root! –" Everything in right subtree is >root! –" Both left and right subtrees are also BST#s! Operations on BST! •" Some can be inherited from binary tree! –" Constructor (for empty tree)! –" Inorder, Preorder, and Postorder traversal! •" Some must be defined ! –" Insert item! –" Delete item! –" Retrieve item! The Node<E> Class! •" Just as for a linked list, a node consists of a data part and links to successor nodes! •" The data part is a reference to type E! •" A binary tree node must have links to both its left and right subtrees! The BinaryTree<E> Class! The BinaryTree<E> Class (continued)! Overview of a Binary Search Tree! •" Binary search tree definition! –" A set of nodes T is a binary search tree if either of the following is true! •" T is empty! •" Its root has two subtrees such that each is a binary search tree and the value in the root is greater than all values of the left subtree but less than all values in the right subtree! Overview of a Binary Search Tree (continued)! Searching a Binary Tree! Class TreeSet and Interface Search Tree! BinarySearchTree Class! BST Algorithms! •" Search! •" Insert! •" Delete! •" Print values in order! –" We already know this, it#s inorder traversal! –" That#s why it#s called “in order”! Searching the Binary Tree! •" If the tree is
    [Show full text]
  • 4 Hash Tables and Associative Arrays
    4 FREE Hash Tables and Associative Arrays If you want to get a book from the central library of the University of Karlsruhe, you have to order the book in advance. The library personnel fetch the book from the stacks and deliver it to a room with 100 shelves. You find your book on a shelf numbered with the last two digits of your library card. Why the last digits and not the leading digits? Probably because this distributes the books more evenly among the shelves. The library cards are numbered consecutively as students sign up, and the University of Karlsruhe was founded in 1825. Therefore, the students enrolled at the same time are likely to have the same leading digits in their card number, and only a few shelves would be in use if the leadingCOPY digits were used. The subject of this chapter is the robust and efficient implementation of the above “delivery shelf data structure”. In computer science, this data structure is known as a hash1 table. Hash tables are one implementation of associative arrays, or dictio- naries. The other implementation is the tree data structures which we shall study in Chap. 7. An associative array is an array with a potentially infinite or at least very large index set, out of which only a small number of indices are actually in use. For example, the potential indices may be all strings, and the indices in use may be all identifiers used in a particular C++ program.Or the potential indices may be all ways of placing chess pieces on a chess board, and the indices in use may be the place- ments required in the analysis of a particular game.
    [Show full text]
  • Binary Search Trees (BST)
    CSCI-UA 102 Joanna Klukowska Lecture 7: Binary Search Trees [email protected] Lecture 7: Binary Search Trees (BST) Reading materials Goodrich, Tamassia, Goldwasser: Chapter 8 OpenDSA: Chapter 18 and 12 Binary search trees visualizations: http://visualgo.net/bst.html http://www.cs.usfca.edu/~galles/visualization/BST.html Topics Covered 1 Binary Search Trees (BST) 2 2 Binary Search Tree Node 3 3 Searching for an Item in a Binary Search Tree3 3.1 Binary Search Algorithm..............................................4 3.1.1 Recursive Approach............................................4 3.1.2 Iterative Approach.............................................4 3.2 contains() Method for a Binary Search Tree..................................5 4 Inserting a Node into a Binary Search Tree5 4.1 Order of Insertions.................................................6 5 Removing a Node from a Binary Search Tree6 5.1 Removing a Leaf Node...............................................7 5.2 Removing a Node with One Child.........................................7 5.3 Removing a Node with Two Children.......................................8 5.4 Recursive Implementation.............................................9 6 Balanced Binary Search Trees 10 6.1 Adding a balance() Method........................................... 10 7 Self-Balancing Binary Search Trees 11 7.1 AVL Tree...................................................... 11 7.1.1 When balancing is necessary........................................ 12 7.2 Red-Black Trees.................................................. 15 1 CSCI-UA 102 Joanna Klukowska Lecture 7: Binary Search Trees [email protected] 1 Binary Search Trees (BST) A binary search tree is a binary tree with additional properties: • the value stored in a node is greater than or equal to the value stored in its left child and all its descendants (or left subtree), and • the value stored in a node is smaller than the value stored in its right child and all its descendants (or its right subtree).
    [Show full text]
  • Pivot Selection Method for Optimizing Both Pruning and Balancing in Metric Space Indexes
    Pivot Selection Method for Optimizing both Pruning and Balancing in Metric Space Indexes Hisashi Kurasawa1, Daiji Fukagawa2, Atsuhiro Takasu3, and Jun Adachi3 1 The University of Tokyo, 2-1-2 Hitotsubashi, Chiyoda-ku, Tokyo, Japan 2 Doshisha University, 1-3 Tatara Miyakodani, Kyotanabe-shi, Kyoto, Japan 3 National Institute of Informatics, 2-1-2 Hitotsubashi, Chiyoda-ku, Tokyo, Japan Abstract. We researched to try to find a way to reduce the cost of nearest neighbor searches in metric spaces. Many similarity search indexes recur- sively divide a region into subregions by using pivots, and construct a tree structure index. A problem in the existing indexes is that they only focus on the pruning objects and do not take into consideration the tree balanc- ing. The balance of the indexes depends on the data distribution and the indexes don’t reduce the search cost for all data. We propose a similar- ity search index called the Partitioning Capacity Tree (PCTree). PCTree automatically optimizes the pivot selection based on both the balance of the regions partitioned by a pivot and the estimated effectiveness of the search pruning by the pivot. As a result, PCTree reduces the search cost for various data distributions. Our evaluations comparing it with four in- dexes on three real datasets showed that PCTree successfully reduces the search cost and is good at handling various data distributions. Keywords: Similarity Search, Metric Space, Indexing. 1 Introduction Finding similar objects in a large dataset is a fundamental process of many applications, such as image completion [7]. These applications can be speeded up by reducing the query execution cost of a similarity search.
    [Show full text]
  • A Set Intersection Algorithm Via X-Fast Trie
    Journal of Computers A Set Intersection Algorithm Via x-Fast Trie Bangyu Ye* National Engineering Laboratory for Information Security Technologies, Institute of Information Engineering, Chinese Academy of Sciences, Beijing, 100091, China. * Corresponding author. Tel.:+86-10-82546714; email: [email protected] Manuscript submitted February 9, 2015; accepted May 10, 2015. doi: 10.17706/jcp.11.2.91-98 Abstract: This paper proposes a simple intersection algorithm for two sorted integer sequences . Our algorithm is designed based on x-fast trie since it provides efficient find and successor operators. We present that our algorithm outperforms skip list based algorithm when one of the sets to be intersected is relatively ‘dense’ while the other one is (relatively) ‘sparse’. Finally, we propose some possible approaches which may optimize our algorithm further. Key words: Set intersection, algorithm, x-fast trie. 1. Introduction Fast set intersection is a key operation in the context of several fields when it comes to big data era [1], [2]. For example, modern search engines use the set intersection for inverted posting list which is a standard data structure in information retrieval to return relevant documents. So it has been studied in many domains and fields [3]-[8]. One of the most typical situations is Boolean query which is required to retrieval the documents that contains all the terms in the query. Besides, set intersection is naturally a key component of calculating the Jaccard coefficient of two sets, which is defined by the fraction of size of intersection and union. In this paper, we propose a new algorithm via x-fast trie which is a kind of advanced data structure.
    [Show full text]
  • Peer-To-Peer Similarity Search Based on M-Tree Indexing
    Peer-to-Peer Similarity Search based on M-Tree Indexing Akrivi Vlachou1?, Christos Doulkeridis1?, and Yannis Kotidis2 1Dept.of Computer and Information Science, Norwegian University of Science and Technology 2Dept.of Informatics, Athens University of Economics and Business fvlachou,[email protected], [email protected] Abstract. Similarity search in metric spaces has several important applications both in centralized and distributed environments. In centralized applications, such as similarity-based image retrieval, usually a server indexes its data with a state- of-the-art centralized metric indexing technique, such as the M-Tree. In this pa- per, we propose a framework for distributed similarity search, where each par- ticipating peer stores its own data autonomously, under the assumption that data is indexed locally by peers using M-Trees. In order to support scalability and efficiency of search, we adopt a super-peer architecture, where super-peers are responsible for query routing. We propose the construction of metric routing in- dices suitable for distributed similarity search in metric spaces. We study the performance of the proposed framework using both synthetic and real data. 1 Introduction Similarity search in metric spaces has received significant attention in centralized set- tings [1, 6], but also recently in decentralized environments [3, 5, 8]. A prominent appli- cation is distributed search for multimedia content, such as images, video or plain text. Existing approaches for P2P metric-based similarity search mainly rely on a structured P2P overlay, which is used to intentionally store objects to peers [5, 8]. The aim is to achieve high parallelism and share the high processing cost over a set of cooperative computers.
    [Show full text]
  • Objectives Objectives Searching a Simple Searching Problem A
    Python Programming: Objectives An Introduction to To understand the basic techniques for Computer Science analyzing the efficiency of algorithms. To know what searching is and understand the algorithms for linear and binary Chapter 13 search. Algorithm Design and Recursion To understand the basic principles of recursive definitions and functions and be able to write simple recursive functions. Python Programming, 1/e 1 Python Programming, 1/e 2 Objectives Searching To understand sorting in depth and Searching is the process of looking for a know the algorithms for selection sort particular value in a collection. and merge sort. For example, a program that maintains To appreciate how the analysis of a membership list for a club might need algorithms can demonstrate that some to look up information for a particular problems are intractable and others are member œ this involves some sort of unsolvable. search process. Python Programming, 1/e 3 Python Programming, 1/e 4 A simple Searching Problem A Simple Searching Problem Here is the specification of a simple In the first example, the function searching function: returns the index where 4 appears in def search(x, nums): the list. # nums is a list of numbers and x is a number # Returns the position in the list where x occurs # or -1 if x is not in the list. In the second example, the return value -1 indicates that 7 is not in the list. Here are some sample interactions: >>> search(4, [3, 1, 4, 2, 5]) 2 Python includes a number of built-in >>> search(7, [3, 1, 4, 2, 5]) -1 search-related methods! Python Programming, 1/e 5 Python Programming, 1/e 6 Python Programming, 1/e 1 A Simple Searching Problem A Simple Searching Problem We can test to see if a value appears in The only difference between our a sequence using in.
    [Show full text]
  • Similarity Searching in Peer-To-Peer Environment
    Masaryk University in Brno Faculty of Informatics ^TIS ftp Similarity Searching in Peer-to-Peer Environment Dissertation Proposal Mgr. David Novák Supervisor: Prof. Ing. Pavel Zezula, CSc. In Brno, January 2006 Supervisor Contents 1 Introduction 1 2 Metrie Space Indexing 2 2.1 Metrie Space Model 2 2.1.1 Metrie Space 2 2.1.2 Similarity Queries 2 2.1.3 Metrie Distance Measures 3 2.2 Metrie Partitioning Principles 5 2.2.1 Ball Partitioning 5 2.2.2 Excluded Middle Partitioning 5 2.2.3 Generalized Hyperplane Partitioning 6 2.2.4 Voronoi-like Partitioning 6 2.3 Search Space Pruning Policies 6 2.3.1 Object-Pivot Distance Constraint 6 2.3.2 Range-Pivot Distance Constraint 7 2.3.3 Double-Pivot Distance Constraint 7 2.3.4 Pivot Filtering 7 2.4 Metric Data Structures 7 2.4.1 Vantage Point Tree 8 2.4.2 Generalized Hyperplane Tree 8 2.4.3 M-Tree 8 2.4.4 D-Index 8 3 Peer-to-Peer Structures 9 3.1 Distributed Hash Tables 9 3.1.1 Chord 9 3.1.2 CAN 10 3.2 One-Dimensional Range Queries 10 3.2.1 P-Grid 10 3.2.2 Skip Graphs & SkipNet 11 3.2.3 P-Tree 12 3.3 Range Queries over Multiple Attributes 12 3.3.1 SCRAP & HSFC-based 12 3.3.2 ZNet 12 3.3.3 MAAN 12 3.3.4 Mercury 13 3.3.5 MURK 13 3.4 Nearest Neighbors Queries 13 3.4.1 pSearch 13 3.4.2 Distributed Quadtree 14 3.4.3 SWAM 14 3.5 Metric Space Structures 14 3.5.1 GHT* 15 3.5.2 MCAN 16 4 Thesis Plan 16 4.1 Overview 16 4.2 Objectives 17 4.3 System Structure Proposal 17 4.4 Future Plans 19 References 20 1 Introduction The diffusion of computer technology into a wide spectrum of human activities leads to formation of a variety of new complex data types.
    [Show full text]
  • Hash Tables & Searching Algorithms
    Search Algorithms and Tables Chapter 11 Tables • A table, or dictionary, is an abstract data type whose data items are stored and retrieved according to a key value. • The items are called records. • Each record can have a number of data fields. • The data is ordered based on one of the fields, named the key field. • The record we are searching for has a key value that is called the target. • The table may be implemented using a variety of data structures: array, tree, heap, etc. Sequential Search public static int search(int[] a, int target) { int i = 0; boolean found = false; while ((i < a.length) && ! found) { if (a[i] == target) found = true; else i++; } if (found) return i; else return –1; } Sequential Search on Tables public static int search(someClass[] a, int target) { int i = 0; boolean found = false; while ((i < a.length) && !found){ if (a[i].getKey() == target) found = true; else i++; } if (found) return i; else return –1; } Sequential Search on N elements • Best Case Number of comparisons: 1 = O(1) • Average Case Number of comparisons: (1 + 2 + ... + N)/N = (N+1)/2 = O(N) • Worst Case Number of comparisons: N = O(N) Binary Search • Can be applied to any random-access data structure where the data elements are sorted. • Additional parameters: first – index of the first element to examine size – number of elements to search starting from the first element above Binary Search • Precondition: If size > 0, then the data structure must have size elements starting with the element denoted as the first element. In addition, these elements are sorted.
    [Show full text]
  • Chapter 13 Sorting & Searching
    13-1 Java Au Naturel by William C. Jones 13-1 13 Sorting and Searching Overview This chapter discusses several standard algorithms for sorting, i.e., putting a number of values in order. It also discusses the binary search algorithm for finding a particular value quickly in an array of sorted values. The algorithms described here can be useful in various situations. They should also help you become more comfortable with logic involving arrays. These methods would go in a utilities class of methods for Comparable objects, such as the CompOp class of Listing 7.2. For this chapter you need a solid understanding of arrays (Chapter Seven). · Sections 13.1-13.2 discuss two basic elementary algorithms for sorting, the SelectionSort and the InsertionSort. · Section 13.3 presents the binary search algorithm and big-oh analysis, which provides a way of comparing the speed of two algorithms. · Sections 13.4-13.5 introduce two recursive algorithms for sorting, the QuickSort and the MergeSort, which execute much faster than the elementary algorithms when you have more than a few hundred values to sort. · Sections 13.6 goes further with big-oh analysis. · Section 13.7 presents several additional sorting algorithms -- the bucket sort, the radix sort, and the shell sort. 13.1 The SelectionSort Algorithm For Comparable Objects When you have hundreds of Comparable values stored in an array, you will often find it useful to keep them in sorted order from lowest to highest, which is ascending order. To be precise, ascending order means that there is no case in which one element is larger than the one after it -- if y is listed after x, then x.CompareTo(y) <= 0.
    [Show full text]
  • P4 Sec 4.1.1, 4.1.2, 4.1.3) Abstraction, Algorithms and ADT's
    Computer Science 9608 P4 Sec 4.1.1, 4.1.2, 4.1.3) Abstraction, Algorithms and ADT’s with Majid Tahir Syllabus Content: 4.1.1 Abstraction show understanding of how to model a complex system by only including essential details, using: functions and procedures with suitable parameters (as in procedural programming, see Section 2.3) ADTs (see Section 4.1.3) classes (as used in object-oriented programming, see Section 4.3.1) facts, rules (as in declarative programming, see Section 4.3.1) 4.1.2 Algorithms write a binary search algorithm to solve a particular problem show understanding of the conditions necessary for the use of a binary search show understanding of how the performance of a binary search varies according to the number of data items write an algorithm to implement an insertion sort write an algorithm to implement a bubble sort show understanding that performance of a sort routine may depend on the initial order of the data and the number of data items write algorithms to find an item in each of the following: linked list, binary tree, hash table write algorithms to insert an item into each of the following: stack, queue, linked list, binary tree, hash table write algorithms to delete an item from each of the following: stack, queue, linked list show understanding that different algorithms which perform the same task can be compared by using criteria such as time taken to complete the task and memory used 4.1.3 Abstract Data Types (ADT) show understanding that an ADT is a collection of data and a set of operations on those data
    [Show full text]
  • Introduction to Hash Table and Hash Function
    Introduction to Hash Table and Hash Function This is a short introduction to Hashing mechanism Introduction Is it possible to design a search of O(1)– that is, one that has a constant search time, no matter where the element is located in the list? Let’s look at an example. We have a list of employees of a fairly small company. Each of 100 employees has an ID number in the range 0 – 99. If we store the elements (employee records) in the array, then each employee’s ID number will be an index to the array element where this employee’s record will be stored. In this case once we know the ID number of the employee, we can directly access his record through the array index. There is a one-to-one correspondence between the element’s key and the array index. However, in practice, this perfect relationship is not easy to establish or maintain. For example: the same company might use employee’s five-digit ID number as the primary key. In this case, key values run from 00000 to 99999. If we want to use the same technique as above, we need to set up an array of size 100,000, of which only 100 elements will be used: Obviously it is very impractical to waste that much storage. But what if we keep the array size down to the size that we will actually be using (100 elements) and use just the last two digits of key to identify each employee? For example, the employee with the key number 54876 will be stored in the element of the array with index 76.
    [Show full text]