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 Apr 12, 2024. It is now read-only.
@jbdeboer found an issue in AngularDart which was implemented the same as AngularJS.
Concerning fetching cached templates within $http, the service is checking xsrf tokens before checking the cache for the template, which was adding ~2ms to template load time for each component that used templateUrl. For a page with 500 components in use (e.g. button components in a table), this could add 1s to page rendering time. See:
$http was previously checking cookies to find an xsrf-token prior to checking
the cache. This caused a performance penalty of about 2ms, which can be very
significant when loading hundreds of template instances on a page.
Fixesangular#7717
$http was previously checking cookies to find an xsrf-token prior to checking
the cache. This caused a performance penalty of about 2ms, which can be very
significant when loading hundreds of template instances on a page.
Fixes#7717
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@jbdeboer found an issue in AngularDart which was implemented the same as AngularJS.
Concerning fetching cached templates within $http, the service is checking xsrf tokens before checking the cache for the template, which was adding ~2ms to template load time for each component that used templateUrl. For a page with 500 components in use (e.g. button components in a table), this could add 1s to page rendering time. See:
angular.js/src/ng/http.js
Line 605 in ff03698
A nice performance gain can be achieved by moving this xsrf logic to after the cache check.
The text was updated successfully, but these errors were encountered: