directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r879257 - in /websites/staging/directory/trunk/content: ./ mavibot/user-guide/2.1-file-format.html mavibot/user-guide/images/nodeLeaf.graphml mavibot/user-guide/images/nodeLeaf.png
Date Fri, 20 Sep 2013 22:36:38 GMT
Author: buildbot
Date: Fri Sep 20 22:36:37 2013
New Revision: 879257

Staging update by buildbot for directory

(with props)
    websites/staging/directory/trunk/content/mavibot/user-guide/images/nodeLeaf.png   (with
    websites/staging/directory/trunk/content/   (props changed)

Propchange: websites/staging/directory/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Fri Sep 20 22:36:37 2013
@@ -1 +1 @@

Modified: websites/staging/directory/trunk/content/mavibot/user-guide/2.1-file-format.html
--- websites/staging/directory/trunk/content/mavibot/user-guide/2.1-file-format.html (original)
+++ websites/staging/directory/trunk/content/mavibot/user-guide/2.1-file-format.html Fri Sep
20 22:36:37 2013
@@ -212,6 +212,12 @@ it's something we might want to change l
 <p>Note that a <em>BTree</em> header can be stored on one or many <em>IOPage</em>s,
depending on its size.</p>
 <p>All in all, when we have more than one <em>BTree</em> stored in the
file, the content of the file which stores the <em>BTree</em> headers will look
like this one :</p>
 <p><img alt="BTrees" src="images/BTree.png" /></p>
+<p>Note that each <em>BTreeHeader</em> has at least one root page, even
if it contains no data. In this schema, we show the root page just after the <em>BTree</em>
it is associated to, but after a few updates, the root page may perfectly well be stored elswhere
on the disk.</p>
+<h4 id="the-nodes-and-leaves">The Nodes and Leaves</h4>
+<p>Nodes and Leaves are logical <em>BTree</em> pages which are serialized
on disk into one to many <em>PageIO</em>s. They have slightly different data structures,
as <em>Node</em>s contains pointers to <em>Leaves</em>, and no data,
while <em>Leaves</em> contains data. In any case, both contain the keys.</p>
+<p>On disk, each <em>Node</em> and <em>Leaf</em> are stored
in <em>PageIO</em>s, as we said. A <em>Node</em> will have pointers
to some other logical pages, and on disk, those pointers will be offset of the first <em>PageIO</em>
used to store the logical page it points to.</p>
+<p>Here is the <em>Node</em> and <em>Leaf</em> data structures
once serialized :</p>
+<p><img alt="Node and Leaf" src="images/nodeLeaf.png" /></p>
     <div class="nav">

Added: websites/staging/directory/trunk/content/mavibot/user-guide/images/nodeLeaf.graphml
Binary file - no diff available.

Propchange: websites/staging/directory/trunk/content/mavibot/user-guide/images/nodeLeaf.graphml
    svn:mime-type = application/xml

Added: websites/staging/directory/trunk/content/mavibot/user-guide/images/nodeLeaf.png
Binary file - no diff available.

Propchange: websites/staging/directory/trunk/content/mavibot/user-guide/images/nodeLeaf.png
    svn:mime-type = image/png

View raw message