Pete Bacon Darwin 0c2ed4c3e5 fix(ngcc): do not use cached file-system (#36687) ... The cached file-system was implemented to speed up ngcc processing, but in reality most files are not accessed many times and there is no noticeable degradation in speed by removing it. Benchmarking `ngcc -l debug` for AIO on a local machine gave a range of 196-236 seconds with the cache and 197-224 seconds without the cache. Moreover, when running in parallel mode, ngcc has a separate file cache for each process. This results in excess memory usage. Notably the master process, which only does analysis of entry-points holds on to up to 500Mb for AIO when using the cache compared to only around 30Mb when not using the cache. Finally, the file-system cache being incorrectly primed with file contents before being processed has been the cause of a number of bugs. For example https://github.com/angular/angular-cli/issues/16860#issuecomment-614694269. PR Close #36687		2020-04-17 16:33:48 -04:00
..
lockfile_with_child_process	fix(ngcc): do not use cached file-system (#36687)	2020-04-17 16:33:48 -04:00
async_locker_spec.ts	build: update jasmine to 3.5 (#34625)	2020-04-08 12:10:34 -07:00
sync_locker_spec.ts	style(ngcc): reformat of ngcc after clang update (#36447)	2020-04-06 09:26:57 -07:00