You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I discovered a significant rendering performance issue in my app. After refactoring a table I was seeing a new significant delay after a click when rendering some table rows.
@pzuraq Asked if I could try with a production build. The performance was significantly better than the development build. He thought perhaps it was another instance of a known issue with "Error slowness"
I have created a simple reproduction of the error here -> https://github.com/dgavey/ember-table-rendering-performance . There is a checkbox that either renders the columns of the table using an each for the column display, or skips the each and just renders every column.
If the checkbox is on, the initial rendering of the table is quite a bit slower than it is when it's off. This was evaluated in a development build.
In a production build, the render time between options seems to be much closer.
In this reproduction the render difference does not seem to be any where near as dramatic as it is in my app, but so far this is the closest I could come to finding where the performance difference was while keeping the reproduction simple.
The text was updated successfully, but these errors were encountered:
…formance.
Removes capturing stack traces for all tracked items, as just calling
`new Error()` ends up taking quite a bit of time.
Fixesemberjs#18834Fixesemberjs#18798
This is extended from a conversation on Discord.
I discovered a significant rendering performance issue in my app. After refactoring a table I was seeing a new significant delay after a click when rendering some table rows.
@pzuraq Asked if I could try with a production build. The performance was significantly better than the development build. He thought perhaps it was another instance of a known issue with "Error slowness"
I have created a simple reproduction of the error here -> https://github.com/dgavey/ember-table-rendering-performance . There is a checkbox that either renders the columns of the table using an each for the column display, or skips the each and just renders every column.
If the checkbox is on, the initial rendering of the table is quite a bit slower than it is when it's off. This was evaluated in a development build.
In a production build, the render time between options seems to be much closer.
In this reproduction the render difference does not seem to be any where near as dramatic as it is in my app, but so far this is the closest I could come to finding where the performance difference was while keeping the reproduction simple.
The text was updated successfully, but these errors were encountered: