From 224716ad9cada3adcf6ac0ad9b262cdb51683e44 Mon Sep 17 00:00:00 2001
From: ocelot-inc <pgulutzan@ocelot.ca>
Date: Mon, 30 Jun 2014 17:22:25 -0600
Subject: [PATCH] Added a note about sophia
---
doc/user/databases.xml | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/doc/user/databases.xml b/doc/user/databases.xml
index 74d8c66207..1b3b226455 100644
--- a/doc/user/databases.xml
+++ b/doc/user/databases.xml
@@ -244,6 +244,17 @@ tarantool> <userinput>s = box.schema.create_space('space55', {id = 555, temporar
...
</programlisting>
</para>
+ <para>
+ <bridgehead renderas="sect4">The Sophia alternative storage engine</bridgehead>
+ There are actually two storage engines for Tarantool: memtx (the in-memory storage engine)
+ and Sophia (the on-disk storage engine). To specify that the engine should be Sophia,
+ add a clause: <code>engine = 'sophia'</code>. The manual concentrates on memtxt because it is
+ the default and has been around longer. But Sophia is a working key-value engine and will especially
+ appeal to users who like to see data go directly to disk, so that recovery time might be
+ shorter and database size might be larger. On the other hand, with Sophia the maximum
+ number of indexes is 1, and the maximum number of fields per index is 1.
+ For architectural explanations and benchmarks, see sphia.org.
+ </para>
</listitem>
</varlistentry>
--
GitLab