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: 2018     Entry time: 20 Nov 2020     In reply to: 2017
Author: Stefan Ritt 
Topic: Forum 
Subject: History plot consuming too much memory 
 > 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 guess this will not be network limiting but CPU limiting of the mhttpd process. But I'm 
not 100% sure, depends on the actual hardware. But even if we improve the history 
retrieval to "window only", the user could request all data form 2010 to 2020. So one 
would need some code which estimates the amount of data, then tell the user "do you really 
want that?". But still, a novice user can simply click "yes" without much of a thought. So 
in conclusion I believe proper user training is better than software limits. Like the 
other guy "I did 'rm -rf /', and now nothing works any more, can you help?".

Stefan
ELOG V3.1.4-2e1708b5