Memory usage on large datasets

[jmo (ecoles)]

My team is running into a memory leak and we are hoping that there may be a solution you guys can help with. We are trying to support large cell grids. We are testing with 50 columns and 10K Rows (500K cells) as we believe this will be larger than most usage of the control but something we needed to support.

We did not want to infinite scroll and add data as it was found, we wanted the full grid of cells to be generated when we knew how large the dataset was. So the user could freely move around the grid without waiting for data to load.

Our method generates the cells, then allows the user to scroll around the grid of cells. After they stop scrolling we load the data specific for those cells in the view port. So far this functionality has been great.

Our issue is that after we navigate away from the page and try to recover the memory usage of the Grid, we cannot get IE11 to release the memory.

Here is a JSBin of an example http://jsbin.com/sapuzavima/1/edit?html,js,output

[aleksandra_budnik]

Hi @jmo

sorry for a delay. Do you experience the same issue with the latest version?

We have fixed a similar issue https://github.com/handsontable/handsontable/issues/3646 in the v0.31.0

[jmo (ecoles)]

Hi Aleksandra, thanks for the response after a week without a response I was losing hope. Finally able to address this issue again, we are still experiencing it in our Version 0.24. I will try to upgrade the library although in the past we have seen some functionality conflicts between HoT and Angular, and it seems they have still not been addressed.

ngHandsontable - Cell edit causes ng-model issue

Thanks for sharing @murph1329 We will check this issue but please use the ngHandsontable Github for reporting bugs related to Angular version. It is available at: https://github.com/handsontable/ngHandsontable Thanks in advance!

Issue: ngHandsontable - Cell edit causes ng-model issue

Issue: AngularJS binding does not update when IE's clear button is clicked

[aleksandra_budnik]

Hi @jmo

yes, there were some issues related to compatibility to AngularJS. The case is that as world is taking big steps towards Angular 4 we decided to also take a step further and create an Angular wrapper. It will be available at https://github.com/handsontable/angular2-handsontable. Currently there is only a repository booked but we will start the work in May.

[jmo (ecoles)]

Having updated our project we are still seeing large and increasing memory usage. Libraries HoT-0.31.2 and ngHoT-0.13.0

Are there any other suggestions? Unfortunately after an effort to move to Angular, moving to Angular2 wouldn’t be possible at the moment.

Is there a way you can suggest to work with this much Data? Preferably without paging or infinite scrolling we want to move to any section of the grid without having to load more cells (we already have the content dynamically loading in)[.

This issue is currently preventing us from pushing our new page to production. We were hoping this library would allow us to upgrade our functionality, but with such a performance hit in IE we cannot move forward.

[aleksandra_budnik]

Hi @jmo

I have asked one of our developers for help and he told me that you could check the memory usage on a blank Handsontable implementation (if it is still rising) as he has tested http://output.jsbin.com/taxopofahu and did not find any related action in a task manager.
Also if creating a demo is too time-consuming you can pause parts of the code that can cause it one by one to see what is causing the issue.

When it comes to performance in IE we have done a lot of changes but IE is pretty limited itself. As a lot of our Clients also experience the performance issues on IE we decided to try to find a solution in this quarter (trello roadmap: https://trello.com/c/646bhIv1/83-improve-scrolling-performance-in-ie-firefox) but we are not sure about the success.