ArangoDB: Is it bad if the data or index no longer fits into RAM?

Dear ArangoDB Community,

I am wondering if this is bad when we use ArangoDB, and if, unfortunately, the data index + is too large and no longer fits in RAM. What happens then? Does it terribly disrupt system performance?

For TokuMX, which is a very fun MongoDB plugin (TokuMX offers the ACID Transactions I need), they say this is a problem at all! Even TokuMX clearly says on its website that for TokuMX it does not really matter if the data index + is not suitable in RAM.

In addition, for MongoDB, corresponding to TokuMX, we can limit the use of RAM to certain commands.

For my web project, I would like to decide which database I will use, I do not want to change later. The RAM of my database server is no more than 500 MB right now, and it is used connectively by the NodeJS server. Therefore, both are sitting on the same server.

On this server I have 1 Nodejs Server and 2 database instances running. Thus, I am comparing TokuMX and ArangoDb with the TOP command in linux to verify RAM usage. Both types of data have a tiny collection for testing. And the TOP command on Linux tells me: ArangoDB: RES: 128 MB in use, and for TokuMX it says only 9 MB (!!) Res means: the actual, actually used physical RAM that I discovered. So, the difference is already huge ... thanks and many greetings. In addition, the use of a virtual drum is very different. 5 GB for arangodb. and just 300 MB for tokumx.

+4
source share
2 answers

ArangoDB - API-. V8 API. Mac 3 5 V8. 81M. 1 ( ) 80M. V8

./bin/arangod -c etc/relative/arangod.conf testbase3 --scheduler.threads 1 --server.threads 2

34M, 1, 24M. , -, 14 .

( mongodb arangodb redis) , . , , , . , , . , ArangoDB MongoDB.

: ArangoDB? , .

+5

. , ArangoDB Node, . . , . , , , -. . ACID javascript - ! , ArangoDB. , Nodejs, ACID, ArangoDb. , javascript, ArangoDb , , . javascript ACID. , , , , , FOXX ACID? , , , , . foxx . ?

+1
source

Source: https://habr.com/ru/post/1543059/


All Articles