Rendering the graph on smaller timescales (typically <= 100ns on normal browsers and logs as shown) will cause chrome to run out of memory and crash the program.
[Issue created by ashayas: 2016-11-03]
[Last updated on bitbucket: 2016-11-04]
[Comment created by ashayas: 2016-11-04]
One issue is that this is ram dependent but I think if we can assume a more modest ram size for the user and determine thresholds and give this error accordingly it would be best. I will figure out a way that works best.
[Comment created by bestchai: 2016-11-04]
Can you detect when this is a problem (e.g., when number of events is above some limit)? in this case you can show an error to the user telling them that they should select a larger granularity value, or a value above 100 (the more precise the better).
Rendering the graph on smaller timescales (typically <= 100ns on normal browsers and logs as shown) will cause chrome to run out of memory and crash the program.
[Issue created by ashayas: 2016-11-03]
[Last updated on bitbucket: 2016-11-04]
[Comment created by ashayas: 2016-11-04]
One issue is that this is ram dependent but I think if we can assume a more modest ram size for the user and determine thresholds and give this error accordingly it would be best. I will figure out a way that works best.
[Comment created by bestchai: 2016-11-04]
Can you detect when this is a problem (e.g., when number of events is above some limit)? in this case you can show an error to the user telling them that they should select a larger granularity value, or a value above 100 (the more precise the better).