44821a918c
Summary: Add telemetry to main memgraph binary Add resource usage collector Add telemetry flag Change telemetry collector logic Fix utils compilation Add timestamp Add first version of interactive test Started working on test runner Implement all tests Flake8 on runner.py Integrate test with Apollo Add TODO Reviewers: buda, teon.banek Reviewed By: buda, teon.banek Subscribers: pullbot Differential Revision: https://phabricator.memgraph.io/D1419
100 lines
3.7 KiB
Plaintext
100 lines
3.7 KiB
Plaintext
# Default Memgraph Configuration
|
|
#
|
|
# This is the default configuration for memgraph. Settings from this file will
|
|
# be overridden by a configuration file in '$HOME/.memgraph/config', so you can
|
|
# keep this file intact. Additional configuration can be specified in a file
|
|
# pointed to by 'MEMGRAPH_CONFIG' environment variable or by passing arguments
|
|
# on the command line.
|
|
#
|
|
# Each configuration setting is of the form: '--setting-name=value'.
|
|
|
|
## Database
|
|
|
|
# IP address the server should listen on.
|
|
--interface=0.0.0.0
|
|
|
|
# Port the server should listen on.
|
|
--port=7687
|
|
|
|
# Number of workers used by the Memgraph server. By default, this will be the
|
|
# number of processing units available on the machine.
|
|
# --num-workers=8
|
|
|
|
# Interval, in seconds, when the garbage collection (GC) should run. GC is used
|
|
# for releasing memory that is no longer needed. For example, deleted graph
|
|
# elements which cannot be seen by any running or new transactions. If set to
|
|
# -1 the GC will never run (use with caution, memory will never get released).
|
|
--gc-cycle-sec=30
|
|
|
|
# If Memgraph detects there is less available RAM than the given number in MB,
|
|
# it will log a warning.
|
|
--memory-warning-threshold=1024
|
|
|
|
# The telemetry collects data about the machine that is executing the database
|
|
# (CPU, Memory, OS and Kernel Information) and data about the database runtime
|
|
# (CPU usage, Memory usage, Vertices and Edges count). It is used to provide a
|
|
# better product, easy to disable and does not collect any sensitive data.
|
|
--telemetry-enabled=true
|
|
|
|
## Query
|
|
#
|
|
# Various settings related to openCypher query execution.
|
|
|
|
# Maximum allowed query execution time, in seconds. Any queries exceeding this
|
|
# limit will be aborted. Setting to -1 removes the limit.
|
|
--query-execution-time-sec=30
|
|
|
|
# Cache generated query execution plans. This speeds up planning repeated
|
|
# queries which produce multiple complex execution plans. The downside is that
|
|
# some executions may use inferior plans if the database state changed. To
|
|
# disable caching, set to false.
|
|
#--query-plan-cache=false
|
|
|
|
# Time to live for cached query plans, in seconds. This tries to minimize the
|
|
# downside of caching by evicting old plans after the given time.
|
|
#--query-plan-cache-ttl=60
|
|
|
|
## Durability
|
|
#
|
|
# Memgraph can store database state to persistent storage. Two mechanisms
|
|
# are used: snapshots store the total current database state while write-ahead
|
|
# logs store small changes incrementally. They are used in tandem to provide
|
|
# fast and storage-efficient persistence. Some aspects of snapshot taking
|
|
# are configurable, while write-ahead logging is pre-configured for optimal
|
|
# performance.
|
|
--durability-enabled=true
|
|
|
|
# Path to the directory where snapshots and write-ahead log files will be stored.
|
|
--durability-directory=/var/lib/memgraph/durability
|
|
|
|
# Recover the database on startup.
|
|
--db-recover-on-startup=true
|
|
|
|
# Interval of taking snapshots, in seconds. If set to -1, the snapshot feature
|
|
# will be turned off.
|
|
--snapshot-cycle-sec=300
|
|
|
|
# Create a snapshot when closing Memgraph.
|
|
--snapshot-on-exit=true
|
|
|
|
# Maximum number of kept snapshots. Old snapshots will be deleted to make room
|
|
# for new ones. If set to -1, the number of kept snapshots is unlimited.
|
|
--snapshot-max-retained=3
|
|
|
|
## Logging
|
|
|
|
# Path to where the log should be stored.
|
|
--log-file=/var/log/memgraph/memgraph.log
|
|
|
|
# If true, log messages will go to stderr in addition to logfiles.
|
|
#--also-log-to-stderr=true
|
|
|
|
## Additional Configuration Inclusion
|
|
|
|
# Include additional configuration from this file. Settings with the same name
|
|
# will override previously read values. Note, that reading the configuration,
|
|
# which called '--flag-file' will continue after inclusion. Therefore, settings
|
|
# after '--flag-file' may override the included ones.
|
|
#--flag-file=another.conf
|
|
|