ArangoDB Performance

A Lot have been said Performance of ArangoDB, but this blog is to aim for the testing the ArangoDB in terms of "How to Performance Test"

The Tool that have been used is Jmeter and Arango bench.

But lets check some of the configurations for ArangoDB

1. Threads =0

This configuration is available in in the "arangod.conf"

Default value is 0, gives ArangoDB the free hand to choose the number of threads based on the available CPU.

2. authentication = true

This is enabling the HTTPS entry for the ArangoDB

If you plan to stop the HTTPS , update the following entry,

endpoint = tcp://127.0.0.1:8529

3. The Port that you assign to ArangoDB will be hard clamped to ArangoDB unless the following entry is enabled

reuse-address = true

4. For enabling the server stats

statistics = false (This creates an extra overhead, which can be enabled only for debugging purpose)

5. Scheduler : This indicate the number of threads that can be used for I/O. Making threads =0 will enable the ArangoDB to manipulate the threads for I/O operation according to the VM configuration.

6. LOG :

Two modes are available

1. Trace

2. Debug

Depending on log configuration for the we need to change that accordingly.

we can also specify the log path :

file = /var/log/arangodb3/arangod.log

NOTE : If we change anything in the please make a point to restart the ArangoDB service.

Performance Testing With ArangoBench :

ArangoBench is the default tool that is provided with the ArangoDB that can be used for bench-marking purpose.

The configuration file for the ArangoBench is placed in the file --> arangobench.conf

As aragobench comes pre installed we need not install it any more

Commands to check Arangobench is working or not

1. arangobench

Output :