Back Midas Rome Roody Rootana
  Midas DAQ System  Not logged in ELOG logo
Entry  19 Nov 2020, Joseph McKenna, Forum, History plot consuming too much memory 
    Reply  19 Nov 2020, Stefan Ritt, Forum, History plot consuming too much memory 
       Reply  20 Nov 2020, Joseph McKenna, Forum, History plot consuming too much memory 
          Reply  20 Nov 2020, Stefan Ritt, Forum, History plot consuming too much memory 
          Reply  27 Nov 2020, Konstantin Olchanski, Forum, History plot consuming too much memory 
       Reply  27 Nov 2020, Konstantin Olchanski, Forum, History plot consuming too much memory 
    Reply  27 Nov 2020, Konstantin Olchanski, Forum, History plot consuming too much memory 
       Reply  27 Nov 2020, Konstantin Olchanski, Forum, History plot consuming too much memory 
Message ID: 2017     Entry time: 20 Nov 2020     In reply to: 2016     Reply to this: 2018   2031
Author: Joseph McKenna 
Topic: Forum 
Subject: History plot consuming too much memory 
Poking at the behavior of this, its fairly clear the slow response is from the data 
being loaded off an HDD, when we upgrade this system we will allocate enough SSD 
storage for the histories.

Using Firefox has resolved this issue for the user's project here

Taking this down a tangent, I have a mild concern that a user could temporarily 
flood our gigabit network if we do have faster disks to read the history data. Have 
there been any plans or thoughts on limiting the bandwidth users can pull from 
mhttpd? I do not see this as a critical item as I can plan the future network 
infrastructure at the same time as the next system upgrade (putting critical data 
taking traffic on a separate physical network).

> Of course one can only
> load that specific window, but when the user then scrolls right, one has to
> append new data to the "right side" of the array stored in the browser. If the
> user jumps to another location, then the browser has to keep track of which 
> windows are loaded and which windows not, making the history code much more 
> complicated. Therefore I'm only willing to spend a few days of solid work
> if this really becomes a problem. 

For now the user here has retrieved all the data they need, and I can direct others 
towards mhist in the near future. Being able to load just a specific window would be 
very useful in the future, but I comprehend how it would be a spike in complexity.
ELOG V3.1.4-2e1708b5