asked on September 6, 2024
I am investigating using the Flexmonster pivot grid in an application in our company. We'll be using ~ 100,000 objects. I got it up and running with the trial version but noticed that after scrolling around to see how it performed with streaming updates the memory footprint for the tab was very high and not dropping down.
I did some googling and found the one million row example https://www.flexmonster.com/demos/js/one-million-rows/ and this page has the same issue. If you slowly scroll top to bottom over and over then the memory for the tab slowly builds up and never drops back down.
I did some investigation and at least found that in the memory snapshot there are no unexpected detached div elements for the rows, this means that the div elements that are destroyed when scrolling are being garbage collected correctly. This would indicate that the issue is in the pivot grid itself.
⋅ September 9, 2024
Hello, Joseph!
Thank you for bringing this behavior to our attention.
Our team has reproduced the case on our end only during extensive scrolling through millions of rows of data. Could you please let us know more about your use case and how much your user experience relies on this issue?
Looking forward to hearing from you.
Kind regards,
Solomiia
⋅ September 10, 2024
Hi Solomiia,
This behaviour is unfortunately a deal breaker for us. We would like to use flexmonster as the performance is the best of all the pivot grids we have tried however some users will have the page open for extended periods and so this memory leak would just increase until it affected their other work.
Thanks,
Jo
⋅ September 10, 2024
Hello, Joseph!
Thank you for your swift response. We are happy to hear that you're pleased with Flexmonster's performance.
We understand the inconveniences mentioned memory leak can cause to your users. Our Dev team will research possible improvements for the described behavior. We will get back to you with the research results with the ETA September 30th.
Our team will notify you about any updates on the matter.
Feel free to reach out to us if any other questions arise.
Kind regards,
Solomiia
⋅ September 30, 2024
Hi, it is the 30th, have you had any updates from your dev team?
⋅ September 30, 2024
Hello, Joseph!
Thank you for getting in touch. Hope you are doing well.
Our team is happy to inform you that the memory management of data for the virtual grid was improved.
Mentioned improvements are included in the 2.9.87 version of Flexmonster: https://www.flexmonster.com/release-notes/version-2-9-87/.
You are welcome to update the component: https://www.flexmonster.com/doc/updating-to-the-latest-version/.
Please let us know if the update works well for you.
Kind regards,
Solomiia
⋅ October 1, 2024
Thanks, will give this a try
⋅ October 1, 2024
Tried it out and this works well. Memory does build up when scrolling but then looks to correctly get GC'd. Still very much in PoC stage but will likely look to use flexmonster for our pivot grid. Thanks for quick turnaround.
⋅ October 1, 2024
Hello, Joseph!
Thank you for your swift feedback.
We are glad to hear that our memory improvements work well on your end.
Our team is happy to assist you should you decide to use Flexmonster further.
Feel free to reach out to us in case of any questions.
Kind regards,
Solomiia
