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
There should be a mechanism to not have to evaluate JS (costly) multiple time for the same domain name. I've been profiling my app which does a lot of requests, and this is a bottleneck.
The text was updated successfully, but these errors were encountered:
This issue is tricky because of timeRange(). Though that function may be rarely used, its existence means caching to reduce JS calls could introduce incorrect behaviour. pac_context_for_url() is different approach to avoiding JS evaluation.
I did a quick performance check with the following notebook snippet:
Right now, only the proxy parsing gets cached:
There should be a mechanism to not have to evaluate JS (costly) multiple time for the same domain name. I've been profiling my app which does a lot of requests, and this is a bottleneck.
The text was updated successfully, but these errors were encountered: