Joe Spencer
Joe Spencer
i'd be open to PRs for this.
dang! 500 paths is a lot! are the external references downloaded when your server starts up? if so, i'd bet that's where most of your slowness is happening.
well, with 500 paths, i can only imagine how many operations you have. if you were to `require` all those files without calling `.initialize`, how long does it take?
right, but during `.initialize`, it's going to call `require` for each of the paths right? what's the output of this? ``` find ./paths-dir -type f | wc -l ```
depending on how many require calls the framework has to make, it may make sense to use `args.operations`.
oh, well that changes everything lol using `console`, can you log before and after times before and after the initialize call?
wow. well, that's definitely slow. it would be nice if we had a way to optionally turn on profiling logs
i can offer theories, but it would be amazing if you could profile this locally: https://nodejs.org/en/docs/guides/simple-profiling/ i assume it's as slow or slower on your local machine?
https://github.com/kogosoftwarellc/open-api/blob/master/packages/openapi-framework/src/util.ts#L150
That copy function is actually called a lot: https://github.com/kogosoftwarellc/open-api/blob/master/packages/openapi-framework/index.ts The point was to guarantee a deep copy in case the rest of the framework alerted the original doc in some...