Skip to content

Conversation

asgerf
Copy link
Contributor

@asgerf asgerf commented Mar 5, 2020

Restricts computation of barrier guard dominance and barrier guard functions to those reachable by exploratory flow.

Evaluation on smoke-test shows an improvement of a few percent and (a slightly earlier revision) on nightly is also leaning on positive but is missing a final tweak which I'm evaluating now.

Commit-by-commit review recommended.

@asgerf asgerf added JS Awaiting evaluation Do not merge yet, this PR is waiting for an evaluation to finish labels Mar 5, 2020
@asgerf asgerf requested a review from a team as a code owner March 5, 2020 16:51
@asgerf
Copy link
Contributor Author

asgerf commented Mar 6, 2020

Evaluation looks ok for tuple counts, but the wall clock time was unusually biased time - I'll do some sanity checks.

@asgerf asgerf force-pushed the js/late-barrier-guards branch from 0d6c2e5 to 2ef21ea Compare March 7, 2020 15:13
@asgerf asgerf removed the Awaiting evaluation Do not merge yet, this PR is waiting for an evaluation to finish label Mar 10, 2020
@asgerf
Copy link
Contributor Author

asgerf commented Mar 10, 2020

Sanity checks went fine. @erik-krogh can you review this?

Copy link
Contributor

@erik-krogh erik-krogh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, everything makes sense 👍

I'm was suspicious of that performance evaluation, as both the wall-clock and dpm agreed that performance was generally worse, and only tuple counts showed an improvement.
But your sanity checks worked out, so 👍 from here.

@semmle-qlci semmle-qlci merged commit e3fed39 into github:master Mar 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants