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
{{ message }}
This repository has been archived by the owner on Dec 31, 2022. It is now read-only.
I am loading LABjs using the async snippet and providing it a list of scripts to fetch. no ".wait()" .
But if you see the waterfall(Internet Explorer 8) linked to above, requests 8 to 13 - the ones injected by Labjs, have roughly 50ms gap between starting the requests. This is not a browser limitation since there is no other network activity going on to saturate the browsers limitations. Also, the cpu is also not busy during that time since no other script is being parsed/executed.
This gap between start of request is not seen on firefox and ie9 RC.
Couldnt find anything in the source which could be adding a settimeout for 50 or 60ms..
The text was updated successfully, but these errors were encountered:
I don't really have an answer. There's no artificial delays inside of LABjs. It sounds possibly like a bug or network connection timing issue in IE8, especially since other browsers/versions don't exhibit the problem.
please see : http://www.webpagetest.org/result/110228_4D_3bb68ed39c46b859b9a84778f4c530a9/5/details/
I am loading LABjs using the async snippet and providing it a list of scripts to fetch. no ".wait()" .
But if you see the waterfall(Internet Explorer 8) linked to above, requests 8 to 13 - the ones injected by Labjs, have roughly 50ms gap between starting the requests. This is not a browser limitation since there is no other network activity going on to saturate the browsers limitations. Also, the cpu is also not busy during that time since no other script is being parsed/executed.
This gap between start of request is not seen on firefox and ie9 RC.
Couldnt find anything in the source which could be adding a settimeout for 50 or 60ms..
The text was updated successfully, but these errors were encountered: