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: 2029     Entry time: 27 Nov 2020     In reply to: 2028
Author: Konstantin Olchanski 
Topic: Forum 
Subject: History plot consuming too much memory 
>
> With the current code, we are limited to loading history data up to 50% of
> the javascript memory limit.
>

The javascript memory limit itself seems to be a moving target. (google javascript 
memory limit, and good luck!).

Historically, javascript did not have any memory or cpu use limits, but with
the raise of abusive web sites, bitcoin miners, etc, I see browsers clamp down
on allowed/allocated CPU use (inactive tabs are throttled down). memory use
is already clamped down severely, on a 64 GB computer, a browser tab
can only allocate a handful of GBs.

This throttling of browser tabs is already intrusive enough that we need
to be careful in programming midas web pages. for examples throttled events
are not firing at the same rate or in the same order as in active tabs.

One logical conclusion of these restrictions could be that, eventually,
google-chrome permits only just enough cpu and memory to run gmail.

K.O.
ELOG V3.1.4-2e1708b5