opened
abhisheksinghrana
username_0
There are lot of setTimeout and message handler issues are coming while scrolling table component because of that page gets hanged or sometime start responding slowly.

<img width="880" alt="violation issue" src="https://user-images.githubusercontent.com/29912424/77610024-90261f00-6f47-11ea-99e8-d8ef75b800c7.png">
Table component - setTimeout and message handler violation issues
issue
created
cal-smith
username_1
Hey @username_0 sorry this has taken so long, we've been pretty swamped with some of the v4/v11 work ... I did some preliminary testing, and it does seem like as the rows increase some of the interactions do slow down quite significantly. That being said, in order for it to slow down to a noticeable degree I had to add quite a few rows - have you explored using pagination as a way to reduce the number of rows visible on screen?
comment
created
asudoh
username_2
Weighing in and @username_1 has a good point. Another suggestion I have for the issue author is following below steps:

1. Go to Performance tab
2. Hit the Record (icon) button
3. Run the use case that shows the console log in question
4. Click on the Stop button
5. Hit the Save profile (icon) button and select the download location
6. Post the downloaded file here

![performance-tab-1](https://user-images.githubusercontent.com/1259051/82101142-a29e2700-9746-11ea-813b-d18c23cb87a9.gif)

In this way, the team can have much clearer insight of what the offending code is, without having to spending time to guess how to re-create the performance problem. Hope this helps!

BTW agreed with @username_1 that pagination is a "must" for ensuring performance. Without it, the page can have excessive amount of DOM nodes that Carbon Angular library would have no control over for the performance.
comment
created
ninja511
username_3
Any updates on this?
comment
closed
ninja511
username_3
issue
created
ninja511
username_3
closing for now - reopen if needed
comment