<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>PhD Workshop, August</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Spatial Indexing on Flash-Based Solid State Drives</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Anderson C. Carniel Supervised by Cristina D. A. Ciferri University of Sa ̃ o Paulo</institution>
          ,
          <country country="BR">Brazil</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2018</year>
      </pub-date>
      <volume>27</volume>
      <issue>2018</issue>
      <abstract>
        <p>The use of a spatial index is fundamental to process spatial queries on spatial database systems. With the growing use of ash-based Solid State Drives (SSDs), designing spatial indices for these storage devices has gained increasing attention. Hence, while there are spatial indices dedicated to magnetic disks (i.e., disk-based spatial indices ), the literature has focused on to propose ash-aware spatial indices that consider the intrinsic characteristics of SSDs, such as the asymmetric costs of reads and writes. However, the research to date has not been able to establish a ash-aware spatial index that actually exploits all the bene ts of SSDs. The principal goal of this PhD work is to propose an e cient ash-aware spatial indexing method by taking into account the system implications introduced by SSDs. The main preliminary result of this PhD is eFIND, a generic framework that transforms a disk-based spatial index into an e cient ash-aware spatial index. Performance tests showed that, compared to the state of the art, eFIND improved the construction of spatial indices from 60% to 77%, and the spatial query processing from 22% to 23%.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. INTRODUCTION</title>
      <p>
        Spatial database systems largely employ spatial indices to
process spatial queries [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], such as intersection range queries
(IRQs). A wide range of spatial indices like the R-tree
and its variants assume that the indexed spatial objects are
stored in magnetic disks (i.e., Hard Disk Drives - HDDs).
Hence, they consider the slow mechanical access and the
cost of search and rotational delay of disks in their design;
we term them as disk-based spatial indices.
      </p>
      <p>
        On the other hand, there is an increasing number of
spatial database applications requiring the use of spatial indices
to retrieve e ciently spatial objects stored in ash-based
Solid State Drives (SSDs) [
        <xref ref-type="bibr" rid="ref2 ref5">5, 2</xref>
        ]. In fact, SSDs have been
widely used as secondary storage in database servers. In
contrast to HDDs, SSDs have a smaller size, lighter weight,
lower power consumption, better shock resistance, and faster
reads and writes.
      </p>
      <p>
        SSDs have also intrinsic characteristics that introduce
several system implications [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. A well-known characteristic is
that a write requires more time and power consumption than
a read. In addition, SSDs require an erase-before-update
operation to rewrite a page since they only are capable of
writing to empty pages. To deal with these characteristics,
some ash-aware spatial indices have been proposed in the
literature [
        <xref ref-type="bibr" rid="ref10 ref11 ref7 ref9">11, 9, 10, 7</xref>
        ].
      </p>
      <p>
        However, current ash-aware spatial indices do not
exploit all the bene ts of SSDs. First, the impact of SSDs
on the spatial indexing context is understudied, particularly
for designing of e cient ash-aware spatial indices. Second,
existing indices assume that the random read is the fastest
operation of SSDs and thus, they execute an excessive
number of reads to minimize the number of random writes. But,
this behavior degenerates SSD performance [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. Third, there
is no special treatment to minimize the e ects of interleaved
reads and writes, which also negatively impact SSD
performance [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. Finally, existing ash-aware spatial indices
handle ine cient in-memory data structures.
      </p>
      <p>
        In this PhD work, we aim to solve the aforementioned
problems by pursuing three objectives. The rst objective
is to understand the impact of SSDs on the spatial indexing
context by means of empirical evaluations. To this end,
we analyzed the performance behavior of spatial indices on
HDDs and SSDs [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. The goal was to check whether a spatial
index that shows the best results on the HDD also shows the
best results on the SSD and vice-versa. Hence, we analyzed
what should be modi ed in existing spatial indices in order
to achieve good performance on SSDs.
      </p>
      <p>
        The second objective is to propose a set of design goals
for designing ash-aware spatial indices. To this end, we
correlated the intrinsic characteristics of SSDs and
observations from our empirical studies. The proposed design
goals were validated through the implementation of the e
cient Framework for spatial INDexing on SSDs (eFIND) [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
eFIND is a generic framework that transforms a disk-based
spatial index into a ash-aware spatial index without
requiring modi cations in the structure and algorithms of the
underlying index. Instead, eFIND e ciently changes the way
in which reads and writes are performed on the SSD. This
characteristic allows us to incorporate eFIND into
existing spatial database systems with low implementation costs.
Our experiments showed that eFIND is very e cient since
it provides e cient data structures speci cally developed to
achieve each design goal.
      </p>
      <p>The third, and last, objective is to propose a novel e
cient and robust ash-aware spatial index. Currently, we are
developing this index by taking the design goals of eFIND
as a basis and by modifying the internal structure of the
index to exploit the bene ts of SSDs. An initial idea is to
consider structures based on the R-tree, where levels
nearest to leaf nodes might have an update-intensive workload.
Thus, minimizing the number of split operations on these
levels will lead to a decreasing number of writes to SSDs.
Further, high levels of the tree can be bu ered to minimize
the number of reads from SSDs since the nodes in such levels
are not frequently modi ed and are read-intensive.</p>
      <p>The rest of this paper is organized as follows. Section 2
surveys related work. Section 3 summarizes our studies on
the impact of SSDs on the spatial indexing. Section 4
introduces our design goals and eFIND. Finally, Section 5
concludes the paper and presents future work.</p>
    </sec>
    <sec id="sec-2">
      <title>RELATED WORK</title>
      <p>
        We classify the existing approaches that study spatial
indexing on SSDs in the following groups: (i) works that
conduct experimental evaluations, and (ii) proposals of
ashaware spatial indices. With respect to the rst group, there
are some performance studies that analyze the a ect of SSDs
on the spatial indexing. Unfortunately, a common limitation
of these studies is that they do not vary parameters that
impact the performance of spatial indices, such as the page
size (i.e., node size). An example of performance study is [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ],
which empirically analyzes the R*-tree in the computation
of k-nearest neighbor queries on HDDs and SSDs.
      </p>
      <p>
        With respect to the second group, the existing ash-aware
spatial indices are inspired by unidimensional indices for
ash memory (e.g., the LA-tree [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]) and often attempt to
port the R-tree to be ash-aware. We detail the main
characteristics of ash-aware spatial indices as follows.
      </p>
      <p>
        The RFTL [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] is a rst straightforward extension of the
R-tree. It does not change the structure of the R-tree and
only employs a write bu er to deal with the well-known poor
performance of random writes of SSDs. The main problem
of RFTL is the ushing operation because it writes all
modi cations stored in the write bu er, requiring high elapsed
times. Another problem is related to the data durability.
This means that the modi cations stored in the write bu er
are lost after a system crash or power failure.
      </p>
      <p>
        The LCR-tree [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] emerged to improve the ushing
operation of RFTL by using a log-structured format to store the
modi cations in its write bu er. However, the management
of this write bu er requires an additional computational cost
to keep the log-structured format. Another problem is the
lack of a ushing policy for the ushing operation, which
still requires long times to write all bu ered modi cations.
      </p>
      <p>
        FAST [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] generalized the write bu er for allowing the
transformation of any disk-based hierarchical index into a
ash-aware index, such as the creation of the FAST R-tree
from the R-tree. The FAST's bu er improves the search
performance by storing the results of index modi cations. In
addition, FAST provides a specialized ushing algorithm to
create space for new modi cations whenever the write bu er
is full. Another characteristic of FAST is its support for data
durability. However, FAST faces the following problems.
First, it can write a ushing unit containing a node without
modi cation, resulting in unnecessary writes to the SSD.
This is due to the static creation of ushing units as soon
      </p>
      <sec id="sec-2-1">
        <title>Linear R-tree (HDD)</title>
        <p>Linear R-tree (SSD)</p>
      </sec>
      <sec id="sec-2-2">
        <title>Quadratic R-tree (HDD)</title>
        <p>
          Quadratic R-tree (SSD)
900
as nodes are created in the index. Second, the modi cations
of a node are stored in a list that allows repeated elements.
That means this list can store the result of old modi cations
and a full scan is needed to retrieve the most recent version
of a node. These problems impact on FAST performance,
as detailed in [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ].
        </p>
        <p>
          The FOR-tree [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] improves the ushing algorithm of FAST
by dynamically creating ushing units with only the modi
cations stored in the write bu er. It also abolishes splitting
operations of full nodes by allowing over owed nodes stored
in the main memory. When a speci c number of accesses
to an over owed node is reached, a merge-back operation
is invoked. This operation eliminates over owed nodes by
inserting them as entries in its parent, growing up the tree
if needed. However, the number of accesses of an over owed
root node is never incremented in an insertion operation. As
a consequence, spatial objects are stored in the over owed
root node in a sequential form when building an index. This
critical problem disallowed us to create spatial indices over
voluminous datasets.
3.
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>THE IMPACT OF FLASH MEMORY ON</title>
    </sec>
    <sec id="sec-4">
      <title>THE SPATIAL INDEXING CONTEXT</title>
      <p>
        In this section, we provide a summary of an empirical
analysis of spatial indices on HDDs and SSDs that was
conducted in our work [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Considering a dataset extracted
from the OpenStreetMap containing 534,926 regions
(speci ed in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]), here we report the elapsed time when creating
R-trees (varying the split algorithm) and R*-trees on an
HDD and SSD (Figure 1). In general, the index page size
of 4KB gathered the best performance results for all spatial
indices. For this page size, the SSD showed better
performance results with performance gains between 4% and 16%
over the HDD.
      </p>
      <p>
        On the other hand, for the index page sizes greater than
8KB we obtained best performance results by using the
HDD. For these page sizes, the construction of spatial
indices on the SSD showed a performance loss ranging from
6% to 38% over the HDD. This result could be considered
as counter-intuitive since SSDs often have faster reads and
writes than HDDs. However, the main reason for this
performance degradation is due to the interleaved writes and
reads during the index construction. This kind of
performance behavior is well studied in the literature, such as
discussed in [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. In addition, the lack of a special treatment
for random writes was also determinant since writes are the
most expensive operations of SSDs.
      </p>
      <p>The results suggested that the direct use of existing
diskbased spatial indices does not guarantee e ciency.
Therefore, we should design ash-aware spatial indices that
consider the intrinsic characteristics of SSDs. This topic is
addressed in Section 4.</p>
    </sec>
    <sec id="sec-5">
      <title>DESIGNING EFFICIENT FLASH-AWARE</title>
    </sec>
    <sec id="sec-6">
      <title>SPATIAL INDICES</title>
      <p>Although the intrinsic characteristics of SSDs have been
well studied in the literature, it remains unclear how to deal
with them to deliver good spatial indexing performance. We
solve this problem by specifying a set of design goals for
ash-aware spatial indices (Section 4.1), and by proposing
eFIND (Section 4.2).
4.1</p>
    </sec>
    <sec id="sec-7">
      <title>Design Goals</title>
      <p>Our ve design goals are inspired by analysis of
experimental evaluations on SSDs (Section 3) and techniques used
by existing indices for ash memory (Section 2). These
design goals should be employed as a basis to create e cient
and robust ash-aware spatial indices. We detail each design
goal as follows.</p>
      <p>
        Goal 1 - Avoid random writes. Random writes are
expensive and can lead to erase-before-update operations,
bad block management, and poor performance of internal
SSD algorithms [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. To achieve Goal 1, a ash-aware spatial
index should employ an e cient in-memory bu er, called
write bu er, to store the most recent modi cations of the
index. Whenever the write bu er is full, a ushing algorithm
should be executed, which should write sequentially a set of
modi cations to the SSD as speci ed in Goal 2.
      </p>
      <p>
        Goal 2 - Dynamically pick modi cations to be
sequentially ushed. A ushing operation that ushes all
modi cations contained in the write bu er degenerates
performance and might writes index pages frequently
modied [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. To achieve Goal 2, a ash-aware spatial index
should include a specialized ushing algorithm consisting of
a ushing policy and a ushing unit creator. The
ushing policy should pick the modi ed index pages to be
written, according to distinct criteria (e.g., number of modi
cations, and the moment of its last modi cation). The ushing
unit creator should create a ushing unit as sequential index
pages, following the ushing policy, and determine the size
of data that is written to the SSD in each ushing operation.
Goal 3 - Avoid excessive random reads in frequent
locations. The common assumption that the random read
is the fastest operation of SSDs is not always valid because
of the read disturbance management [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. To achieve Goal 3,
a ash-aware spatial index should use an in-memory bu er
dedicated to reads, called read bu er. Thus, instead of
performing a random read directly from the SSD to obtain a
frequently accessed index page, the index page can be
obtained from the read bu er. Further, the management of the
read bu er should include a read bu er replacement policy,
such as the LRU.
      </p>
      <p>
        Goal 4 - Avoid interleaved reads and writes. Mixing
reads and writes negatively a ect SSD performance because
of the interference between these operations [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. To achieve
Goal 4, a ash-aware spatial index should use read and write
bu ers together with a temporal control, which temporally
stores the identi ers of the last read and written index pages
to aid in the management of these bu ers.
      </p>
      <p>Goal 5 - Provide data durability. System crashes and
power failures impact the consistency of the index since
modi cations stored in the write bu er are lost. To achieve
Goal 5, a ash-aware spatial index should use a log-structured
approach that sequentially saves non- ushed modi cations
in a log le.</p>
      <p>To the best of our knowledge, there is no ash-aware
spatial index that ful lls all these design goals. Existing
ashaware spatial indices do not improve the performance of
reads and do not avoid interleaved reads and writes. Among
them, FAST provides the best characteristics (Section 2).
Therefore, we consider FAST as the state of the art in
spatial indexing for SSDs by comparing it in our experiments.
4.2</p>
      <p>eFIND as a Solution</p>
      <p>
        This section details eFIND, a generic and e cient
framework that transforms a disk-based spatial index into a
ashaware spatial index. The eFIND's architecture consists of
three sophisticated managers to meet the requirements of
the design goals introduced in Section 4.1. More details
about eFIND are given in [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>Bu er Manager. It leverages two in-memory bu ers to
deal with random writes and reads. The rst one is the
write bu er, which stores the most recent index modi
cations from insert, update, and delete operations (Goal 1).
The second one is the read bu er, which caches index pages
frequently accessed in search operations (Goal 3).
Flushing Manager. It contains three interacting
components to perform a ushing operation. The rst component
is the ushing unit creator, which builds ushing units by
grouping sequential index pages. The second component is
the ushing policy, which ranks ushing units according to
di erent criteria (Goal 2). The last component is the
temporal control of reads and writes, which avoids interleaved
reads and writes (Goal 4).</p>
      <p>Log Manager. It guarantees data durability (Goal 5) by
keeping a log of all modi cations stored in the write bu er
and of ushing operations. Modi cations lost after a system
crash can be recovered by dispatching the restart operation.
This manager also compacts the log le to decrease the cost
of the space utilization.</p>
      <p>Now, we discuss the performance gains of an extension of
eFIND against the state of the art, FAST. The experiments
and their results are detailed as follows.</p>
      <p>
        Setup. We used a dataset from the OpenStreetMap
containing 1,485,866 regions that represent the buildings of Brazil
(speci ed in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]). We compared the FAST R-tree, and the
eFIND R-tree. They employed an in-memory bu er of 512KB.
We used the best parameter values for these con gurations
and executed two workloads: (i) index construction, and (ii)
execution of IRQs [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Here we show the results of the
execution of 100 IRQs with query windows of 0.001% of the area
of Brazil. The running environment employed was FESTIval
(available at https://github.com/accarniel/festival), a
PostgreSQL extension implemented during this PhD that
allows us to conduct performance tests of spatial indices.
Finally, we conducted the experiments on a Kingston SSD
V300 of 480GB.
800
eFIND R-tree
      </p>
      <p>FAST R-tree
36
27
18
9
Index Construction. As shown in Figure 2a, the eFIND
R-tree overcame the FAST R-tree for all employed page
sizes. Its performance gains were very expressive, ranging
from 60% to 77%. The eFIND R-tree exploited the
bene ts of the SSDs because it is based on the design goals
de ned in Section 4.1. The contribution of the read bu er
to obtain these results was signi cantly relevant even using
a relatively small portion of the bu er size (20%). Another
important contribution was the use of the temporal
control, which guaranteed that frequently accessed index pages
were stored beforehand in the read bu er. Further, eFIND
improved the space utilization of the write bu er by
leveraging e cient data structures to manage index modi cations.
This led to the faster retrieval of index pages, re ecting in
the elapsed time when building spatial indices in the SSD.
Spatial Query Processing. Figure 2b depicts that, for
both con gurations, larger page sizes provided better elapsed
times since more entries are loaded into the main memory,
requiring fewer reads from the SSD. For these page sizes
(16KB and 32KB), the eFIND R-tree showed gains of 22%
and 23% respectively mainly because of the read bu er,
which contributes to reducing the number of reads.</p>
    </sec>
    <sec id="sec-8">
      <title>CONCLUSIONS AND OUTLOOK</title>
      <p>This paper describes a PhD work on spatial indexing on
SSDs. The PhD encompasses three main goals: (i)
understand the impact of SSDs on the spatial indexing context,
(ii) design methods for e cient ash-aware spatial indexing,
and (iii) propose a new e cient ash-aware spatial index.
The rst goal was achieved through extensive experimental
evaluations to analyze the performance behavior of spatial
indices on HDDs and SSDs. As a result, we studied the de
ciencies of disk-based spatial indices when applied to SSDs.
With this study, we then achieved the second goal of this
PhD by proposing eFIND, which is based on a set of design
goals that exploit the bene ts of SSDs. eFIND is a generic
framework that can be applied in a wide range of spatial
indices, such as the R-tree and its variants, without changing
original algorithms of the underlying index. eFIND is also
e cient, showing expressive performance gains that ranged
from (i) 60% to 77% when building spatial indices and from
(ii) 22% to 23% when processing spatial queries.</p>
      <p>The next activities of this PhD include the proposal of a
novel ash-aware spatial index. By using the design goals of
eFIND and other ndings of the conducted experiments, we
plan to design a tree structure that exploits the bene ts of
SSDs. For instance, we learned from the experiments that
a high number of writes is performed from splitting
operations in the bottom levels of the tree. Thus, by allowing
over owed nodes in the bottom levels, we could improve the
performance of the index in maintenance operations without
impairing the spatial organization of the index. Finally, the
novel ash-aware spatial index will be evaluated by means of
extended performance tests, that is, with other types of
spatial indices in addition to IRQs, and other spatial datasets.</p>
    </sec>
    <sec id="sec-9">
      <title>ACKNOWLEDGMENTS</title>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>D.</given-names>
            <surname>Agrawal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Ganesan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Sitaraman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Diao</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Singh</surname>
          </string-name>
          .
          <article-title>Lazy-adaptive tree: An optimized index structure for ash devices</article-title>
          .
          <source>VLDB Endowment</source>
          ,
          <volume>2</volume>
          (
          <issue>1</issue>
          ):
          <volume>361</volume>
          {
          <fpage>372</fpage>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>A. C.</given-names>
            <surname>Carniel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R. R.</given-names>
            <surname>Ciferri</surname>
          </string-name>
          , and
          <string-name>
            <given-names>C. D. A.</given-names>
            <surname>Ciferri</surname>
          </string-name>
          .
          <article-title>Analyzing the performance of spatial indices on hard disk drives and ash-based solid state drives</article-title>
          .
          <source>Journal of Inf. and Data Management</source>
          ,
          <volume>8</volume>
          (
          <issue>1</issue>
          ):
          <volume>34</volume>
          {
          <fpage>49</fpage>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>A. C.</given-names>
            <surname>Carniel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R. R.</given-names>
            <surname>Ciferri</surname>
          </string-name>
          , and
          <string-name>
            <given-names>C. D. A.</given-names>
            <surname>Ciferri</surname>
          </string-name>
          .
          <article-title>A generic and e cient framework for spatial indexing on ash-based solid state drives</article-title>
          .
          <source>In European Conf. on Advances in Databases and Information Systems</source>
          , pages
          <fpage>229</fpage>
          {
          <fpage>243</fpage>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>A. C.</given-names>
            <surname>Carniel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R. R.</given-names>
            <surname>Ciferri</surname>
          </string-name>
          , and
          <string-name>
            <given-names>C. D. A.</given-names>
            <surname>Ciferri</surname>
          </string-name>
          .
          <article-title>Spatial datasets for conducting experimental evaluations of spatial indices</article-title>
          .
          <source>In Satellite Events of the Brazilian Symp. on Databases</source>
          , pages
          <volume>286</volume>
          {
          <fpage>295</fpage>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>T.</given-names>
            <surname>Emrich</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Graf</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.-P.</given-names>
            <surname>Kriegel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Schubert</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Thoma</surname>
          </string-name>
          .
          <article-title>On the impact of ash SSDs on spatial indexing</article-title>
          .
          <source>In Int. Work. on Data Management on New Hardware</source>
          , pages
          <fpage>3</fpage>
          <issue>{8</issue>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>V.</given-names>
            <surname>Gaede</surname>
          </string-name>
          and
          <string-name>
            <given-names>O.</given-names>
            <surname>Gu</surname>
          </string-name>
          <article-title>nther. Multidimensional access methods</article-title>
          .
          <source>ACM Comp. Surveys</source>
          ,
          <volume>30</volume>
          (
          <issue>2</issue>
          ):
          <volume>170</volume>
          {
          <fpage>231</fpage>
          ,
          <year>1998</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>P.</given-names>
            <surname>Jin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Xie</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Wang</surname>
          </string-name>
          , and
          <string-name>
            <given-names>L.</given-names>
            <surname>Yue</surname>
          </string-name>
          .
          <article-title>Optimizing R-tree for ash memory</article-title>
          .
          <source>Expert Systems with Applications</source>
          ,
          <volume>42</volume>
          (
          <issue>10</issue>
          ):
          <volume>4676</volume>
          {
          <fpage>4686</fpage>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>M.</given-names>
            <surname>Jung</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Kandemir</surname>
          </string-name>
          .
          <article-title>Revisiting widely held SSD expectations and rethinking system-level implications</article-title>
          .
          <source>In ACM SIGMETRICS Int. Conf. on Measurement and Modeling of Computer Systems</source>
          , pages
          <fpage>203</fpage>
          {
          <fpage>216</fpage>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Lv</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Cui</surname>
          </string-name>
          , and
          <string-name>
            <given-names>X.</given-names>
            <surname>Chen</surname>
          </string-name>
          .
          <string-name>
            <surname>Log-Compact R-tree</surname>
          </string-name>
          :
          <article-title>An e cient spatial index for SSD</article-title>
          .
          <source>In Int. Conf. on Database Systems for Advanced Applications</source>
          , pages
          <volume>202</volume>
          {
          <fpage>213</fpage>
          ,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>M.</given-names>
            <surname>Sarwat</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. F.</given-names>
            <surname>Mokbel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>X.</given-names>
            <surname>Zhou</surname>
          </string-name>
          , and
          <string-name>
            <given-names>S.</given-names>
            <surname>Nath</surname>
          </string-name>
          .
          <article-title>Generic and e cient framework for search trees on ash memory storage systems</article-title>
          .
          <source>GeoInformatica</source>
          ,
          <volume>17</volume>
          (
          <issue>3</issue>
          ):
          <volume>417</volume>
          {
          <fpage>448</fpage>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>C.-H. Wu</surname>
            ,
            <given-names>L.-P.</given-names>
          </string-name>
          <string-name>
            <surname>Chang</surname>
            , and
            <given-names>T.-W.</given-names>
          </string-name>
          <string-name>
            <surname>Kuo</surname>
          </string-name>
          .
          <article-title>An e cient R-tree implementation over ash-memory storage systems</article-title>
          .
          <source>In ACM SIGSPATIAL Int. Conf. on Advances in Geographic Information Systems</source>
          , pages
          <fpage>17</fpage>
          {
          <fpage>24</fpage>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>