#When I add a new value, it appears that it lasts much longer in 'scripting'
10 messages · Page 1 of 1 (latest)
I would argue about considering "so much longer" (compared to what?) an interval of 52 ms.
Keep in mind that array is tracked by @for, thus on top of the push you got to account its internal logic.
Wouldn't it be possible for scripting to take less time? I think 52ms every time an element is added or modified may not be a good experience.
on 2500?
2500 of what?
Doesn't the graph says the toal elapsed time of the whole operation can take from 600 to 2500 ms?
oh you meant that
So you are saying that cannot decrease the 'scripting' ms.
I say that's doesn't look like the main culprit of the time occured to complete the task.
And in a "highest level environment" like a browser's interpreter it's not easy to strip down a 50ms subtask.