We have updated Flexmonster Software License Agreement, effective as of September 30, 2024. Learn more about what’s changed.

Memory consumption increases on updateData() is called for high frequency real time updates

Answered
kiran bangar asked on August 23, 2023

Hi,
Memory consumption of browser (chrome) increases on updateData() is called for high frequency real time updates. It is around 1k to 1.5k/rps(records per second). We are updating it at a time after buffering for 2 seconds. Resulting in unresponsive page due to lack of memory and crashing eventually.
 
Is there any optimized way to do the above operation to update realtime data which is very frequent and large.
 
Thank you in advance.

3 answers

Public
Solomiia Andrusiv Solomiia Andrusiv Flexmonster August 25, 2023

Hello, Kiran!
 
Thank you for reaching out to us.
 
We kindly ask you for the following details about your use case:

  1. What is the size of the initial dataset?
  2. Do these mentioned 1-1.5K records contain the new members and numeric values, or the new numeric values only?
  3. Is this update partial, or does the data in updateData() function contain some old and some new records?

This information would help us greatly to provide you with a more case-specific solution.
 
Looking forward to hearing from you.
 
Kind regards,
Solomiia

Public
kiran bangar August 26, 2023

Hi,
Below are the details of our use case 
1. What is the size of the initial dataset? - 10000+ records
2. Do these mentioned 1-1.5K records contain the new members and numeric values, or the new numeric values only? -  new members and numeric values
3. Is this update partial, or does the data in updateData() function contain some old and some new records? - old and some new records

Thanks for response. Kindly suggest the better way to address this.

Public
Solomiia Andrusiv Solomiia Andrusiv Flexmonster August 29, 2023

Hello, Kiran!
 
Thank you for the provided details about your data source.
 
If we understand you correctly, the initial dataset has 10k rows, and every second, we are adding 1-1.5k rows to it. This means that the size of the dataset increases up to 70k rows for the first minute and will be growing with every next minute.
Kindly note that the in-browser memory has limited capacity, and it is the expected behavior of the page to crash when you reach this limit.
 
We suggest trying the Flexmonster Data Server tool. This way, we can move all the calculations to the server side and cache some data, which reduces the browser load.
You can find more details about Flexmonster Data Server in our docs: https://www.flexmonster.com/doc/intro-to-flexmonster-data-server/.
 
Hope you will find our answer helpful.
 
Kind regards,
Solomiia

Please login or Register to Submit Answer