0c2ed4c3e5
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
31 lines
854 B
JavaScript
31 lines
854 B
JavaScript
#!/usr/bin/env node
|
|
/**
|
|
* @license
|
|
* Copyright Google Inc. All Rights Reserved.
|
|
*
|
|
* Use of this source code is governed by an MIT-style license that can be
|
|
* found in the LICENSE file at https://angular.io/license
|
|
*/
|
|
import {mainNgcc} from './src/main';
|
|
import {parseCommandLineOptions} from './src/command_line_options';
|
|
|
|
// CLI entry point
|
|
if (require.main === module) {
|
|
process.title = 'ngcc';
|
|
const startTime = Date.now();
|
|
const options = parseCommandLineOptions(process.argv.slice(2));
|
|
(async () => {
|
|
try {
|
|
await mainNgcc(options);
|
|
if (options.logger) {
|
|
const duration = Math.round((Date.now() - startTime) / 1000);
|
|
options.logger.debug(`Run ngcc in ${duration}s.`);
|
|
}
|
|
process.exitCode = 0;
|
|
} catch (e) {
|
|
console.error(e.stack || e.message);
|
|
process.exit(1);
|
|
}
|
|
})();
|
|
}
|