Using it for realtime timeseries, the memory exploded to 2GB

[perkasajob]

I am wondering, whether it can be used for realtime timeseries chart ?

[nicolaskruchten]

Can you tell us a bit more about your use case? How often were you adding points? We’re you removing points as well from the beginning of the series? Many traces did you have? Etc

…

On Mon, Oct 8, 2018 at 08:51 perkasajob ***@***.***> wrote: I am wondering, whether it can be used for realtime timeseries chart ? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#104>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMbA-jcn48gmLwObiEKgTDJdBPW-xdTks5ui0pEgaJpZM4XM3VF> .

[perkasajob]

My setup on Chromium browser, using redux-saga, dva js to be precise, the data coming in every seconds, following is the reducer:

setRtData2(state, action) {
        if(state.rtData.length >1000)
            state.rtData.shift()
        return {
          ...state,
          rtData: [...state.rtData, action.payload],
        };
 },

and render is following :

<Plot
   data={[
   {    x: rtData?rtData.x:[],
        y: rtData?rtDatay.y:[],
        type: 'scatter',
        mode: 'lines+points',
        marker: {color: '#19d3f3'},
        name: 'M1',
    },]}
/>

test using 1000 points, 2 lines (result in 2000 points) in a plot, yes, I did shift array after 1000 points
I tried to use ringjs as ring buffer, but it did not help either.
I am aware react store previous state, to detect changes, is it possible, all the state history piling up to drive memory out of control ?
starting from 300mb RAM, increased, until it reached exceed 2Gb after about almost an hour

any other information required ?

[perkasajob]

a false alarm, it seems the complex of redux, somewhere has caused memory leak, disassembled to the bones, problem disappeared, thank you for attention.

[nicolaskruchten]

Ok, glad it worked out!

…

On Wed, Oct 10, 2018 at 03:04 perkasajob ***@***.***> wrote: a false alarm, it seems the complex of redux, somewhere has caused memory leak, disassembled to the bones, problem disappeared, thank you for attention. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#104 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAMbA2fIITHLgpyAkmRm9O8i08RgKDDXks5ujZvggaJpZM4XM3VF> .