memgraph/tests/benchmark
Teon Banek 9f460914ed Separate distributed implementation of GraphDbAccessor
Summary:
GraphDbAccessor is now constructed only through GraphDb. This allows the
concrete GraphDb to instantiate a concrete GraphDbAccessor. This allows
us to use virtual calls, so that the implementation may be kept
separate. The major downside of doing things this way is heap allocation
of GraphDbAccessor. In case it turns out to be a real performance
issues, another solution with pointer to static implementation may be
used.

InsertVertexIntoRemote is now a non-member function, which reduces
coupling. It made no sense for it to be member function because it used
only the public parts of GraphDbAccessor.

Reviewers: msantl, mtomic, mferencevic

Reviewed By: msantl

Subscribers: pullbot

Differential Revision: https://phabricator.memgraph.io/D1504
2018-07-26 09:16:39 +02:00
..
data_structures RingBuffer - buffer on heap instead of stack 2017-11-02 12:07:23 +01:00
query Separate distributed implementation of GraphDbAccessor 2018-07-26 09:16:39 +02:00
CMakeLists.txt Split GraphDb to distributed and single node files 2018-07-20 10:48:38 +02:00
edge_storage.cpp Edge storage benchmark added 2017-09-08 13:12:20 +02:00
expansion.cpp Separate distributed implementation of GraphDbAccessor 2018-07-26 09:16:39 +02:00
mvcc.cpp Add support for the id function 2018-07-04 22:14:13 +02:00
serialization.cpp Benchmark Cap'n Proto and boost serialization 2018-05-02 12:38:18 +02:00
tx_engine.cpp Benchmark tx::SingleNodeEngine 2018-03-27 15:43:59 +02:00