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: 2031     Entry time: 27 Nov 2020     In reply to: 2017
Author: Konstantin Olchanski 
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.
>

By my measurements, right now our javascript code can reach 30-50-70% of Gige ethernet
bandwidth, so, no, we cannot flood the network just by making history plots.

(we cannot reach 100% because javascript code is not multithreaded,
it cycles through "request new data" and "decode javascript, make plot" states,
and the network is idle in this second state).

>
> Have there been any plans or thoughts on limiting the bandwidth users can pull from 
> mhttpd?
>

10gige networking is here (and 5 and 2.5 Gige, too). I would not worry too much
about saturating 1gige network interfaces.

>
> 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).
>

10gige network between all computers, everything on SSD ZFS arrays, except
bulk data on ZFS HDD arrays (only for cost reasons $$$/TB).

K.O.
ELOG V3.1.4-2e1708b5