1 Reply Latest reply on Dec 31, 2018 3:35 PM by patrick.byrne.0

    VizQL crashing. Memory not released during low usage

    Eric Summers

      We recently started having issues with memory consumption on our server (10.1). Memory usually runs around 70% of capacity and frequently spikes. When it spikes, we will generally see a session ended error because the memory hits capacity and TS ends the vizql session to release it. I know this is standard operation for TS but wondering why VizQL holds onto the memory during low usage times like weekend and nights. If I restart TS, memory drops down to around 20%. I have everything setup to cache the least amount of memory. I would expect if server was actually releasing the memory, it would run closer to the 20% then the 70% during non-usage times. What am I missing in my logic?



      Does Vizql server release the memory back to the system?