topic 'Control' 4.2.e memory footprint in Alfresco Archive

'Control' 4.2.e memory footprint

vincent_ravier — Wed, 18 Dec 2013 15:46:57 GMT

Hi,Given those results after FTP vs Import methods, I tried 4.2.e. Alfresco being way less coupled to Lucene by using SOLR, things get better.However, as we will have about 1k+ files uploaded/day, we are really concerned about server resources, and Alfresco's memory consumption. So, we would like to

Re: 'Control' 4.2.e memory footprint

mrogers — Wed, 18 Dec 2013 19:19:00 GMT

You can also reduce the number of threads and reduce the stack sizes. However you are reducing alfresco's performance. Normally tuning will increase various settings.

However what is the concern here? If you give alfresco memory it will use it, and that shouldn't be a problem, that's just normal operation.

And 1000 docs per day is a fairly trivial import load that shouldn't cause any problems.

Re: 'Control' 4.2.e memory footprint

vincent_ravier — Thu, 19 Dec 2013 08:33:59 GMT

Hi, thanks for pointing thread number and stack size out. We know that reducing alfresco's memory usage will reduce its overall performance. The point is to find out some levers in case we cannot allocate all needed resources with the default parameters. Our 3 VM production servers have like 20MB of memory, each are already running around 5 to 8 VM… So, we won't really be able to allocate more than 4GB to the server's OS running Alfresco. I'm currently running a test, importing 1 million files via FTP. After 350k files, things are looking good, 3GB allocated for java's heap, Alfresco doesn't seems to need more for the moment.

1k files a day won't be stressful, but as each uploaded file is cached, we want to be sure that, like after 60 days java won't go OOM due to cache size in memory. That's all

Re: 'Control' 4.2.e memory footprint

mrogers — Thu, 19 Dec 2013 14:43:06 GMT

3 GB is on the small side however it should be adequate. The rule of thumb is 4GB minimum.

Alfresco should not consume memory over time or in proportion to the number of documents. If it does leak then that's a serious bug.

You want to try and prevent your other VMs competing for resources with Alfresco.

Re: 'Control' 4.2.e memory footprint

vincent_ravier — Thu, 26 Dec 2013 16:23:38 GMT

Hi,
I've configured the JVM to run with a 3GB heap. I've successfully uploaded 450k files. Max heap memory used was around 2,5GB, and went above after around 150k files uploaded. Given that other operations might allocate memory (like searching, putting files in cache), yes, 4GB seems good

Thank you.