-
Notifications
You must be signed in to change notification settings - Fork 1.8k
JS: Various small performance improvements #5240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
80ce22e
to
8599331
Compare
javascript/ql/src/semmle/javascript/frameworks/PropertyProjection.qll
Outdated
Show resolved
Hide resolved
javascript/ql/src/semmle/javascript/frameworks/PropertyProjection.qll
Outdated
Show resolved
Hide resolved
javascript/ql/src/semmle/javascript/frameworks/SystemCommandExecutors.qll
Outdated
Show resolved
Hide resolved
javascript/ql/src/semmle/javascript/frameworks/SystemCommandExecutors.qll
Outdated
Show resolved
Hide resolved
Nice! Could you run evaluations of the whole security suite to make sure we aren't breaking performance somewhere else? |
|
asgerf
approved these changes
Feb 24, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Evaluation on default/TaintedPath.ql.
Makes various predicates run faster by changing the join order.
I found them by running
TaintedPath.ql
onvscode
, and then looking through the clause timing reports and tuple counts.It also makes the
globalVarRef
predicate non-recursive.So we no longer treat e.g.
window.globalThis.global.window
as being a reference to the global object.(The performance benefit of that change is minor, so let me know if you want it reverted).
Summary of how how time is saved by each commit (
TaintedPath.ql
running on VSCode).rearange ArrayIndexingStep to avoid #shared predicate
- saves about 5scache AstNode::getParent
- saves a few secondsmake globalVarRef non recursive
- saves about 200msremove magic from inGuard
- saves about 1-2 secondsoutline callee computation - to avoid many joins on getACall
- saves about 300mschange join order for summarizedHigherOrderCall
- saves about 11schange join order for SystemCommandExecutors - and use ApiGraphs::getACall
- saves about 5s