| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
Fast-track to get this into the 15.14.0 release that's happening in another day-and-a-half or so? |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
PR-URL: #38064 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
| Back | FazBrowse Home | New Git URL |
b0d5e03 introduced an unnecessary performance regression when using path.resolve() on POSIX systems. This commit both removes that regression in that situation and reduces the performance hit when path.posix.resolve() is used directly/indirectly on Windows systems.
The following benchmark results come from a Linux system:
After b0d5e03:
After the new implementation (basically caching the regexp):
After avoiding the transformations from b0d5e03 for POSIX systems (I'm not sure why there is a performance increase in this case, as I would have expected zero or close to zero change, but that's V8 for you):
/cc @Trott @mcollina