Académique Documents
Professionnel Documents
Culture Documents
= + = k
k
n
k m k n T
)
`
+
(
s s
1
min
1
k
k
n
n k
Jump Search Analysis (cont)
Take the derivative and solve for T'(x) = 0
to find the minimum.
This is a minimum when
What is the worst case cost?
Roughly
n k =
n 2
Lessons
We want to balance the work done while
selecting a sublist with the work done while
searching a sublist.
In general, make sub-problems of equal effort.
This is an example of divide and conquer.
What if we extend this to three levels?
Interpolation Search
(Also known as Dictionary Search)
Search L at a position that is appropriate to the
value K.
Repeat as necessary to recalculate p for future
searches.
] 1 [ ] [
] 1 [
L L
L
=
n
K
p
Quadratic Binary Search
(This is easier to analyze.)
Compute p and examine
If then sequentially probe
Until we reach a value less than or equal to K.
Similar for
(
] [ L pn
(
] [ pn K L <
(
... 3 , 2 , 1 ], [ = i n i pn L
(
] [ pn L K >
Quadratic Binary Search (cont)
We are now within positions of K.
ASSUME (for now) that this takes a constant
number of comparisons.
We now have a sublist of size .
Repeat the process recursively.
What is the cost?
n
n
QBS Probe Count
QBS cost is O(log log n) if the number of probes
on jump search is constant.
From Cebysevs inequality, we can show that
on uniformly distributed data, the average
number of probes required will be about 2.4.
Is this better than binary search? Theoretically,
yes (in the average case).
Comparison
n log n log log n Diff
16 4 2 2
256 8 3 2.7
64k 16 4 4
2
32
32 5 6.4
n log n-1 2.4 log log n Diff
16 3 4.8 worse
256 7 7.2 same
64k 15 9.6 1.6
2
32
31 12 2.6
Lists Ordered by Frequency
Order lists by (expected) frequency of
occurrence.
Perform sequential search
Cost to access first record: 1
Cost to access second record: 2
Expected search cost:
. ... 2 1
2 1 n n
np p p C + + + =
Examples(1)
(1) All records have equal frequency.
2 / ) 1 ( /
1
+ = =
=
n n i C
n
i
n
Examples(2)
(2) Geometric Frequency
n i
n i
p
n
i
i
=
s s
=
if 2 / 1
1 1 if 2 / 1
1
{
=
~ ~
n
i
i
n
i C
1
. 2 ) 2 / (
Zipf Distributions
Applications:
Distribution for frequency of word usage in
natural languages.
Distribution for populations of cities, etc.
80/20 rule:
80% of accesses are to 20% of the records.
For distributions following 80/20 rule,
=
~ = =
n
i
e n n n
n n n i i C
1
. log / H / /
. 122 . 0 n C
n
~
Self-Organizing Lists
Self-organizing lists modify the order of
records within the list based on the actual
pattern of record accesses.
Self-organizing lists use a heuristic for
deciding how to reorder the list. These
heuristics are similar to the rules for
managing buffer pools.
Heuristics
1. Order by actual historical frequency of
access. (Similar to LFU buffer pool
replacement strategy.)
2. When a record is found, swap it with the
first record on list.
3. Move-to-Front: When a record is found,
move it to the front of the list.
4. Transpose: When a record is found,
swap it with the record ahead of it.
Text Compression Example
Application: Text Compression.
Keep a table of words already seen,
organized via Move-to-Front heuristic.
If a word not yet seen, send the word.
Otherwise, send (current) index in the table.
The car on the left hit the car I left.
The car on 3 left hit 3 5 I 5.
This is similar in spirit to Ziv-Lempel coding.
Searching in Sets
For dense sets (small range, high percentage of
elements in set).
Can use logical bit operators.
Example: To find all primes that are odd numbers,
compute:
0011010100010100 & 0101010101010101
Document processing: Signature files
286
Indexing
Goals:
Store large files
Support multiple search keys
Support efficient insert, delete, and range
queries
287
Files and Indexing
Entry sequenced file: Order records by time
of insertion.
Search with sequential search
Index file: Organized, stores pointers to
actual records.
Could be organized with a tree or other data
structure.
288
Keys and Indexing
Primary Key: A unique identifier for records.
May be inconvenient for search.
Secondary Key: An alternate search key,
often not unique for each record. Often
used for search key.
289
Linear Indexing (1)
Linear index: Index file organized as a
simple sequence of key/record pointer
pairs with key values are in sorted order.
Linear indexing is good for searching
variable-length records.
290
Linear Indexing (2)
If the index is too large to fit in main
memory, a second-level index might be
used.
291
Tree Indexing (1)
Linear index is poor for insertion/deletion.
Tree index can efficiently support all desired
operations:
Insert/delete
Multiple search keys (multiple indices)
Key range search
292
Tree Indexing (2)
Difficulties when storing tree
index on disk:
Tree must be balanced.
Each path from root to leaf
should cover few disk pages.
293
2-3 Tree
A 2-3 Tree has the following properties:
1. A node contains one or two keys
2. Every internal node has either two children
(if it contains one key) or three children (if it
contains two keys).
3. All leaves are at the same level in the tree,
so the tree is always height balanced.
The 2-3 Tree has a search tree property
analogous to the BST.
294
2-3 Tree Example
The advantage of the 2-3 Tree over the BST
is that it can be updated at low cost.
295
2-3 Tree Insertion (1)
296
2-3 Tree Insertion (2)
297
2-3 Tree Insertion (3)
298
B-Trees (1)
The B-Tree is an extension of the 2-3 Tree.
The B-Tree is now the standard file
organization for applications requiring
insertion, deletion, and key range
searches.
299
B-Trees (2)
1. B-Trees are always balanced.
2. B-Trees keep similar-valued records
together on a disk page, which takes
advantage of locality of reference.
3. B-Trees guarantee that every node in the
tree will be full at least to a certain
minimum percentage. This improves
space efficiency while reducing the
typical number of disk fetches necessary
during a search or update operation.
300
B-Tree Definition
A B-Tree of order m has these properties:
The root is either a leaf or has two children.
Each node, except for the root and the
leaves, has between m/2( and m children.
All leaves are at the same level in the tree,
so the tree is always height balanced.
A B-Tree node is usually selected to match
the size of a disk block.
A B-Tree node could have hundreds of
children.
301
B-Tree Search
Generalizes search in a 2-3 Tree.
1. Do binary search on keys in current node. If
search key is found, then return record. If
current node is a leaf node and key is not
found, then report an unsuccessful search.
2. Otherwise, follow the proper branch and
repeat the process.
302
B
+
-Trees
The most commonly implemented form of the B-
Tree is the B
+
-Tree.
Internal nodes of the B
+
-Tree do not store record --
only key values to guild the search.
Leaf nodes store records or pointers to records.
A leaf node may store more or less records than
an internal node stores keys.
303
B
+
-Tree Example
304
B
+
-Tree Insertion
305
B
+
-Tree Deletion (1)
306
B
+
-Tree Deletion (2)
307
B
+
-Tree Deletion (3)
308
B-Tree Space Analysis (1)
B
+
-Trees nodes are always at least half full.
The B*-Tree splits two pages for three, and
combines three pages into two. In this
way, nodes are always 2/3 full.
Asymptotic cost of search, insertion, and
deletion of nodes from B-Trees is O(log n).
Base of the log is the (average) branching
factor of the tree.
309
B-Tree Space Analysis (2)
Example: Consider a B+-Tree of order 100
with leaf nodes containing 100 records.
1 level B+-tree:
2 level B+-tree:
3 level B+-tree:
4 level B+-tree:
Ways to reduce the number of disk fetches:
Keep the upper levels in memory.
Manage B+-Tree pages with a buffer pool.
Graphs
A graph G = (V, E) consists of a set of
vertices V, and a set of edges E, such that
each edge in E is a connection between a
pair of vertices in V.
The number of vertices is written |V|, and the
number edges is written |E|.
Graphs (2)
Paths and Cycles
Path: A sequence of vertices v
1
, v
2
, , v
n
of length
n-1 with an edge from v
i
to v
i+1
for 1 <= i < n.
A path is simple if all vertices on the path are
distinct.
A cycle is a path of length 3 or more that connects
v
i
to itself.
A cycle is simple if the path is simple, except the
first and last vertices are the same.
Connected Components
An undirected graph is connected if there is
at least one path from any vertex to any
other.
The maximum connected subgraphs of an
undirected graph are called connected
components.
Directed Representation
Undirected Representation
Representation Costs
Adjacency Matrix:
Adjacency List:
Graph ADT
interface Graph { // Graph class ADT
public void Init(int n); // Initialize
public int n(); // # of vertices
public int e(); // # of edges
public int first(int v); // First neighbor
public int next(int v, int w); // Neighbor
public void setEdge(int i, int j, int wght);
public void delEdge(int i, int j);
public boolean isEdge(int i, int j);
public int weight(int i, int j);
public void setMark(int v, int val);
public int getMark(int v); // Get vs Mark
}
Graph Traversals
Some applications require visiting every
vertex in the graph exactly once.
The application may require that vertices be
visited in some special order based on
graph topology.
Examples:
Artificial Intelligence Search
Shortest paths problems
Graph Traversals (2)
To insure visiting all vertices:
void graphTraverse(Graph G) {
int v;
for (v=0; v<G.n(); v++)
G.setMark(v, UNVISITED); // Initialize
for (v=0; v<G.n(); v++)
if (G.getMark(v) == UNVISITED)
doTraverse(G, v);
}
Depth First Search (1)
// Depth first search
void DFS(Graph G, int v) {
PreVisit(G, v); // Take appropriate action
G.setMark(v, VISITED);
for (int w = G.first(v); w < G.n();
w = G.next(v, w))
if (G.getMark(w) == UNVISITED)
DFS(G, w);
PostVisit(G, v); // Take appropriate action
}
Depth First Search (2)
Cost: O(|V| + |E|).
Breadth First Search (1)
Like DFS, but replace stack with a queue.
Visit vertexs neighbors before continuing
deeper in the tree.
Breadth First Search (2)
void BFS(Graph G, int start) {
Queue<Integer> Q = new AQueue<Integer>(G.n());
Q.enqueue(start);
G.setMark(start, VISITED);
while (Q.length() > 0) { // For each vertex
int v = Q.dequeue();
PreVisit(G, v); // Take appropriate action
for (int w = G.first(v); w < G.n();
w = G.next(v, w))
if (G.getMark(w) == UNVISITED) {
// Put neighbors on Q
G.setMark(w, VISITED);
Q.enqueue(w);
}
PostVisit(G, v); // Take appropriate action
}
}
Breadth First Search (3)
Topological Sort (1)
Problem: Given a set of jobs, courses, etc.,
with prerequisite constraints, output the
jobs in an order that does not violate any
of the prerequisites.
Topological Sort (2)
void topsort(Graph G) {
for (int i=0; i<G.n(); i++)
G.setMark(i, UNVISITED);
for (int i=0; i<G.n(); i++)
if (G.getMark(i) == UNVISITED)
tophelp(G, i);
}
void tophelp(Graph G, int v) {
G.setMark(v, VISITED);
for (int w = G.first(v); w < G.n();
w = G.next(v, w))
if (G.getMark(w) == UNVISITED)
tophelp(G, w);
printout(v);
}
Topological Sort (3)
Queue-Based Topsort
void topsort(Graph G) {
Queue<Integer> Q = new AQueue<Integer>(G.n());
int[] Count = new int[G.n()];
int v, w;
for (v=0; v<G.n(); v++) Count[v] = 0;
for (v=0; v<G.n(); v++)
for (w=G.first(v); w<G.n(); w=G.next(v, w))
Count[w]++;
for (v=0; v<G.n(); v++)
if (Count[v] == 0) Q.enqueue(v);
while (Q.length() > 0) {
v = Q.dequeue().intValue();
printout(v);
for (w=G.first(v); w<G.n(); w=G.next(v, w)) {
Count[w]--;
if (Count[w] == 0)
Q.enqueue(w);
}
}
}
Shortest Paths Problems
Input: A graph with weights or costs
associated with each edge.
Output: The list of edges forming the shortest
path.
Sample problems:
Find shortest path between two named vertices
Find shortest path from S to all other vertices
Find shortest path between all pairs of vertices
Will actually calculate only distances.
Shortest Paths Definitions
d(A, B) is the shortest distance from
vertex A to B.
w(A, B) is the weight of the edge
connecting A to B.
If there is no such edge, then w(A, B) = .
Single-Source Shortest Paths
Given start vertex s, find the shortest path from s
to all other vertices.
Try 1: Visit vertices in some order, compute
shortest paths for all vertices seen so far, then
add shortest path to next vertex x.
Problem: Shortest path to a vertex already
processed might go through x.
Solution: Process vertices in order of distance from
s.
Example Graph
Dijkstras Algorithm Example
A B C D E
Initial 0
Process A 0 10 3 20
Process C 0 5 3 20 18
Process B 0 5 3 10 18
Process D 0 5 3 10 18
Process E 0 5 3 10 18
Dijkstras Implementation
// Compute shortest path distances from s,
// store them in D
void Dijkstra(Graph G, int s, int[] D) {
for (int i=0; i<G.n(); i++) // Initialize
D[i] = Integer.MAX_VALUE;
D[s] = 0;
for (int i=0; i<G.n(); i++) {
int v = minVertex(G, D);
G.setMark(v, VISITED);
if (D[v] == Integer.MAX_VALUE) return;
for (int w = G.first(v); w < G.n();
w = G.next(v, w))
if (D[w] > (D[v] + G.weight(v, w)))
D[w] = D[v] + G.weight(v, w);
}
}
Implementing minVertex
Issue: How to determine the next-closest
vertex? (I.e., implement minVertex)
Approach 1: Scan through the table of
current distances.
Cost: O(|V|
2
+ |E|) = O(|V|
2
).
Approach 2: Store unprocessed vertices
using a min-heap to implement a priority
queue ordered by D value. Must update
priority queue for each edge.
Cost: O((|V| + |E|)log|V|)
Approach 1
int minVertex(Graph G, int[] D) {
int v = 0; // Initialize to unvisited vertex;
for (int i=0; i<G.n(); i++)
if (G.getMark(i) == UNVISITED)
{ v = i; break; }
for (int i=0; i<G.n(); i++)
// Now find smallest value
if ((G.getMark(i) == UNVISITED) &&
(D[i] < D[v]))
v = i;
return v;
}
Approach 2
void Dijkstra(Graph G, int s, int[] D) {
int v, w;
DijkElem[] E = new DijkElem[G.e()];
E[0] = new DijkElem(s, 0);
MinHeap<DijkElem> H =
new MinHeap<DijkElem>(E, 1, G.e());
for (int i=0; i<G.n(); i++)
D[i] = Integer.MAX_VALUE;
D[s] = 0;
for (int i=0; i<G.n(); i++) {
do { v = (H.removemin()).vertex(); }
while (G.getMark(v) == VISITED);
G.setMark(v, VISITED);
if (D[v] == Integer.MAX_VALUE) return;
for (w=G.first(v); w<G.n(); w=G.next(v, w))
if (D[w] > (D[v] + G.weight(v, w))) {
D[w] = D[v] + G.weight(v, w);
H.insert(new DijkElem(w, D[w]));
}
}
}
Minimal Cost Spanning Trees
Minimal Cost Spanning Tree (MST)
Problem:
Input: An undirected, connected graph G.
Output: The subgraph of G that
1) has minimum total cost as measured by
summing the values of all the edges in the
subset, and
2) keeps the vertices connected.
MST Example
Prims MST Algorithm
// Compute a minimal-cost spanning tree
void Prim(Graph G, int s, int[] D, int[] V) {
int v, w;
for (int i=0; i<G.n(); i++) // Initialize
D[i] = Integer.MAX_VALUE;
D[s] = 0;
for (int i=0; i<G.n(); i++) {
v = minVertex(G, D);
G.setMark(v, VISITED);
if (v != s) AddEdgetoMST(V[v], v);
if (D[v] == Integer.MAX_VALUE) return;
for (w=G.first(v); w<G.n(); w=G.next(v, w))
if (D[w] > G.weight(v, w)) {
D[w] = G.weight(v, w);
V[w] = v;
}
}
}
Alternate Implementation
As with Dijkstras algorithm, the key issue is
determining which vertex is next closest.
As with Dijkstras algorithm, the alternative is
to use a priority queue.
Running times for the two implementations
are identical to the corresponding
Dijkstras algorithm implementations.
Kruskals MST Algorithm (1)
Initially, each vertex is in its own MST.
Merge two MSTs that have the shortest
edge between them.
Use a priority queue to order the unprocessed
edges. Grab next one at each step.
How to tell if an edge connects two vertices
already in the same MST?
Use the UNION/FIND algorithm with parent-
pointer representation.
Kruskals MST Algorithm (2)
Kruskals MST Algorithm (3)
Cost is dominated by the time to remove
edges from the heap.
Can stop processing edges once all vertices
are in the same MST
Total cost: O(|V| + |E| log |E|).