forked from thinkaurelius/titan
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathinmemorybackend.txt
23 lines (15 loc) · 1.19 KB
/
inmemorybackend.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
[[inmemorystorage]]
InMemory Storage Backend
------------------------
Titan ships with an in-memory storage backend which can be used through the following configuration:
[source, properties]
----
storage.backend=inmemory
----
Alternatively, an in-memory Titan graph can be opened directly in the Gremlin shell:
[source, gremlin]
graph = TitanFactory.build().set('storage.backend', 'inmemory').open()
There are no additional configuration options for the in-memory storage backend. As the name suggests, this backend holds all data in memory. Shutting down the graph or terminating the process that hosts the Titan graph will irrevocably delete all data from the graph. This backend is local to a particular Titan graph instance and cannot be shared across multiple Titan graphs.
Ideal Use Case
~~~~~~~~~~~~~~
The in-memory storage backend was primarily developed to simplify testing (for those tests that do not require persistence) and graph exploration. The in-memory storage backend is NOT meant for production use, large graphs, or high performance use cases. The in-memory storage backend is not performance or memory optimized. All data is stored in the heap space allocated to the Java virtual machine.