-
-
Notifications
You must be signed in to change notification settings - Fork 709
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Perfomance issue onLoad on "larger" page #248
Comments
It sounds like this is a dynamically updating page. Is it possible that this page is repeatedly/recursively calling timeago on the same elements over and over again? |
No. I load the table Dom then on load the plugin. Afterwards not again, On Fri, 30 Oct 2015 at 20:46, Ryan McGeary [email protected] wrote:
|
This is a bit cryptic. If you're manually loading a table DOM, I don't understand how "no" is the answer to whether you're dynamically updating the page DOM? |
During the day the result set grows. The html is built in each refresh. No On Sat, 31 Oct 2015 at 00:32, Ryan McGeary [email protected] wrote:
|
I have a page load with a table, in the morning its about 40 elements, towards the end of the day it grows to 200.
I have other scripts running there but I tracked down that timeago "blocks" the page until all the elements are updated... 👎
"blocks" - Cannot scroll the page or click on any element for 1-3 seconds
I think some optimization may be required as the main page does not mention any limits.
This page could potentially shows thousands of rows with timago applied
Sameple of single row
HTML (after run)
Server C#
On this occasion you can see Chrome reports 1.3 seconds but there is still the update dom afterwards I think. (the monitor shows along time, im debugging so it takes long to start but afterwards it runs as normal)
74 rows @ 1.3 seconds ?
The text was updated successfully, but these errors were encountered: