Skip to main content

Elvis 5 memory configuration

Comment

Do you have corrections or additional information about this article? Leave a comment!
Do you have a question about what is described in this article? Please contact Support.


6 comments

  • Samuli Jokipaltio

    Please provide more memory allocation examples for a node that [also] processes assets. Tools that run, in addition of elvisserver: exiftool, ffmpeg, im, gm, libreoffice, ... require their own memory (AFAIK). And unfortunately, occasionally processing very large assets can cause memory starvation for elvis-server. 

    Examples:

    1. Large setup, process only OS X node with 16 GB RAM.
    Based on this article, java heap size is between 6.4 and 8 GB (40-50%). Why does the elvis-server process require so much memory? Should we not leave as much as possible memory free for processing tools?

    2. Small setup, all-roles Linux server with 16 GB RAM.
    Based on this, java heap size should be 4 GB (25%). I have seen a setup like this crash, when large camera raw or video files are imported. 

    3. Large setup, search-only Linux node with 128 GB RAM
    You recommend java heap size setting of 32G GB (25%). This sounds about right, but how can I be sure this is optimal? 

    Does a job-runner role require additional memory?

    For a running system, what are the indicators that could tell us to increase or decrease java heap size?

    Should we also take account the number of cores a server has - I'd assume a 16 core server would require more memory (running more threads and tools) than a 4 core server?

    And how can I be sure, that memory is optimally allocated in my processing-only nodes? 

    1
  • Maarten van Kleinwee

    Hi Samuli,

    I have passed on your comments and feedback to the development team.

    Regards,

    Maarten van Kleinwee
    Senior Technical Writer, WoodWing Software

    0
  • Sebastian Nafroth

    Hello Maarten,

     

    any progress here?

     

    Thank you.

    0
  • Maarten van Kleinwee

    Hi Sebastian,

     

    Not yet unfortunately. I have brought it to the attention of the team once more. Apologies for the delay.

    Regards,

    Maarten van Kleinwee
    Senior Technical Writer, WoodWing Software

    0
  • Sebastian Nafroth

    Any progress here?

     

    Thank you

    0
  • Maarten van Kleinwee

    The article has been updated.

    Regards,

    Maarten van Kleinwee
    Senior Technical Writer, WoodWing Software

    0

Please sign in to leave a comment.