Next: 13.4 Discussion and Exercises Up: 13. Data Structures for Previous: 13.2 XFastTrie: Searching in Contents
The XFastTrie is a big improvement over the BinaryTrie in terms of
query time--some would even call it an exponential improvement--but
the
and
operations are still not terribly fast.
Furthermore, the space usage,
, is higher than the
other SSet implementation in this book, which all use
space.
These two problems are related; if
operations build a
structure of size
then the
operation requires on
the order of
time (and space) per operation.
The YFastTrie data structure simultaneously addresses both the space
and speed issues of XFastTries. A YFastTrie uses an XFastTrie,
, but only stores
values in
. In this way,
the total space used by
is only
. Furthermore, only one
out of every
or
operations in the YFastTrie
results in an
or
operation in
. By doing this,
the average cost incurred by calls to
's
and
operations is only constant.
The obvious question becomes: If
only stores
/
elements,
where do the remaining
elements go? These elements go
into secondary structures, in this case an extended version of
treaps (Section 7.2). There are roughly
/
of these secondary
structures so, on average, each of them stores
items. Treaps
support logarithmic time SSet operations, so the operations on these
treaps will run in
time, as required.
More concretely, a YFastTrie contains an XFastTrie,
,
that contains a random sample of the data, where each element
appears in the sample independently with probability
.
For convenience, the value
, is always contained in
.
Let
denote the elements stored in
.
Associated with each element,
, is a treap,
, that stores
all values in the range
. This is illustrated
in Figure 13.7.
The
operation in a YFastTrie is fairly easy. We search
for
in
and find some value
associated with the
treap
. When then use the treap
method on
to answer the query. The entire method is a one-liner:
T find(T x) {
return xft.find(new Pair<T>(it.intValue(x))).t.find(x);
}
The first
operation (on
) takes
time.
The second
operation (on a treap) takes 
time, where
is the size of the treap. Later in this section, we will show that
the expected size of the treap is
so that this operation takes
time.13.1
Adding an element to a YFastTrie is also fairly simple--most of
the time. The
method calls
to locate the treap,
, into which
should be inserted. It then calls
to
add
to
. At this point, it tosses a biased coin, that comes
up heads with probability
. If this coin comes up heads,
will be added to
.
This is where things get a little more complicated. When
is added to
, the treap
needs to be split into two treaps
and
.
The treap
contains all the values less than or equal to
;
is the original treap,
, with the elements of
removed.
Once this is done we add the pair
to
. Figure 13.8
shows an example.
boolean add(T x) {
int ix = it.intValue(x);
STreap<T> t = xft.find(new Pair<T>(ix)).t;
if (t.add(x)) {
n++;
if (rand.nextInt(w) == 0) {
STreap<T> t1 = t.split(x);
xft.add(new Pair<T>(ix, t1));
}
return true;
}
return false;
}
|
to
takes
time. Exercise 7.12 shows
that splitting
into
and
can also be done in
expected time. Adding the pair (
,
) to
takes
time,
but only happens with probability
. Therefore, the expected
running time of the
operation is
The
method just undoes the work performed by
.
We use
to find the leaf,
, in
that contains the answer
to
. From
, we get the treap,
, containing
and remove
from
. If
was also stored in
(and
is not equal to
) then we remove
from
and add the
elements from
's treap to the treap,
, that is stored by
's
successor in the linked list. This is illustrated in
Figure 13.9.
boolean remove(T x) {
int ix = it.intValue(x);
Node<T> u = xft.findNode(ix);
boolean ret = u.x.t.remove(x);
if (ret) n--;
if (u.x.x == ix && ix != 0xffffffff) {
STreap<T> t2 = u.child[1].x.t;
t2.absorb(u.x.t);
xft.remove(u.x);
}
return ret;
}
Finding the node
in
takes
expected time.
Removing
from
takes
expected time. Again,
Exercise 7.12 shows that merging all the elements of
into
can be done in
time. If necessary, removing
from
takes
time, but
is only contained in
with
probability
. Therefore, the expected time to remove an element
from a YFastTrie is
.
Earlier in the discussion, we put off arguing about the sizes of treaps in this structure until later. Before finishing we prove the result we need.
be an integer stored in a YFastTrie and let
denote the number of elements in the treap,
, that contains
.
Then
![$ \mathrm{E}[\ensuremath{\mathtt{n}}_\ensuremath{\mathtt{x}}] \le 2\ensuremath{\mathtt{w}}-1$](img1648.png){kind=small}
.
denote the elements stored
in the YFastTrie. The treap
contains some elements greater than
or equal to
. These are
, where
is the only one of these elements in which the biased coin
toss performed in the
method came up heads. In other words,
![$ \mathrm{E}[j]$](img1652.png){kind=small}
is equal to the expected number of biased coin tosses required
to obtain the first heads.13.2 Each coin toss is independent and comes up heads
with probability
, so
![$ \mathrm{E}[j]\le\ensuremath{\mathtt{w}}$](img1654.png){kind=small}
. (See Lemma 4.2
for an analysis of this for the case
.)
Similarly, the elements of
smaller than
are
where all these 
coin tosses come up
tails and the coin toss for
comes up heads. Therefore,
![$ \mathrm{E}[k]\le\ensuremath{\mathtt{w}}-1$](img1658.png){kind=small}
, since this is the same coin tossing experiment considered
previously, but in which the last toss doesn't count. In summary,
, so
![$\displaystyle \mathrm{E}[\ensuremath{\mathtt{n}}_\ensuremath{\mathtt{x}}] = \ma...
...athrm{E}[j] + \mathrm{E}[k] \le 2\ensuremath{\mathtt{w}}-1 \enspace . \qedhere $](img1660.png){kind=small}
|
Lemma 13.1 was the last piece in the proof of the following theorem, which summarizes the performance of the YFastTrie:
-bit integers. A
YFastTrie supports the operations
,
, and
in
expected time per operation. The space used by a
YFastTrie that stores
values is
.
The
term in the space requirement comes from the fact that
always
stores the value
. The implementation could be modified (at the
expense of adding some extra cases to the code) so that it is unnecessary
to store this value. In this case, the space requirement in the theorem
becomes
.
![$ \mathrm{E}[r]=\ensuremath{\mathtt{w}}$](img1636.png){kind=small}
, then
![$ \mathrm{E}[\log r]
\le \log w$](img1637.png){kind=small}
.
never exceeds
. However, this only decreases
, so the
upper bound still holds
