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 was archived by the owner on Feb 22, 2018. It is now read-only.
The angular transformers are sharing a cached resolver state to have faster build times, but this cached resolver is locked while it's updating for async IO.
In pub serve, there are cases where a transformer in a later phase is being invoked before one in an earlier phase. This causes the IO for the first transformer to block waiting on the other transformer, but the second transformer cannot proceed because the first one has the resolver cache locked.
Avoiding the resolver cache completely increases total transformer time by 4x for pub build and 160x for pub serve incremental updates.
I'm investigating a couple of approaches which hopefully will not impact build or update times.
The text was updated successfully, but these errors were encountered:
The angular transformers are sharing a cached resolver state to have faster build times, but this cached resolver is locked while it's updating for async IO.
In pub serve, there are cases where a transformer in a later phase is being invoked before one in an earlier phase. This causes the IO for the first transformer to block waiting on the other transformer, but the second transformer cannot proceed because the first one has the resolver cache locked.
Avoiding the resolver cache completely increases total transformer time by 4x for pub build and 160x for pub serve incremental updates.
I'm investigating a couple of approaches which hopefully will not impact build or update times.
The text was updated successfully, but these errors were encountered: