Hi, 
can you try to disable the server statistics as described here:

https://docs.arangodb.com/3.1/Manual/Administration/Configuration/GeneralArangod.html#toggling-server-statistics

(this will remove the graphs you see in the webinterface)

--server.statistics false


If you don't use foxx queues, you can also disable them:
--foxx.queues false

You should then see that this behaviour stops.

Cheers, 
Willi

Since 
On Thursday, April 27, 2017 at 12:02:11 PM UTC+2, Thomas Weiss wrote:
>
> Hi everyone,
>
> I would like to get your comments concerning the very high memory usage 
> I'm seeing on my production server.
> Some numbers:
> - Running Ubuntu 16.04 and ArangoDB 3.1.15
> - 5 document collections, 12 edge collections
> - Around 200,000 documents
> - A dump takes approximately 50MB of disk space
> - A rather heavy usage of Foxx
>
> Now this take *1.5GB* of memory on that Linux server. I've always been a 
> bit surprised by the memory consumption but at the beginning I thought that 
> ArangoDB required a lot of RAM to run and that was a fixed overhead that 
> would not grow with the data, but I was wrong: it seems that the memory 
> consumption increases linearly with the amount of data. Also for reference, 
> I've a secondary DB (same VM config) that replicates the primary 
> asynchronously and this one consumes more than 1GB as well.
>
> So today I did the following experiment: I dumped the database and 
> restored it on my Mac. I made sure all collections are loaded and had a 
> look at the memory: only *200MB* and it even fell to 50MB for some 
> reason. This makes me think that there could be something wrong with the 
> way I run ArangoDB on Ubuntu or with the system config?
>
> Any comment would be welcome, if you'd like to get the dump to test it on 
> your side I would be happy to share it.
>
> Thanks in advance,
> Thomas
>

-- 
You received this message because you are subscribed to the Google Groups 
"ArangoDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to