3 ms·
Other than good integration with existing command-line tools for log analysis, VictoriaLogs is also optimized for low resource usage. For example, it uses up to
by valyala 3y ago
Other than good integration with existing command-line tools for log analysis, VictoriaLogs is also optimized for low resource usage. For example, it uses up to 30x less RAM and up to 15x less disk space than ElasticSearch on production workloads according to our tests, while providing comparable or better query performance. This allows substituting a 30-node ElasticSearch cluster with a single-node VictoriaLogs, e.g. saving infrastructure costs by 30x. Also, single-node setup is much easier to operate than a cluster, so it allows saving operational costs. And, contrary to ElasticSearch, capacity of a single node of VictoriaLogs scales linearly with the number of available RAM and CPU cores. There is no artificial limit of 32GB RAM per node [1].
[1] https://opster.com/guides/elasticsearch/capacity-planning/elasticsarch-java-heap-size/ https://opster.com/guides/elasticsearch/capacity-planning/el...