Skip to content

Make 'complexity reports' cache per-family, not global#1166

Merged
LebedevRI merged 1 commit intogoogle:mainfrom
LebedevRI:per-family-complexity-reports
Jun 3, 2021
Merged

Make 'complexity reports' cache per-family, not global#1166
LebedevRI merged 1 commit intogoogle:mainfrom
LebedevRI:per-family-complexity-reports

Conversation

@LebedevRI
Copy link
Copy Markdown
Collaborator

While the current variant works, it assumes that all the instances of
a single family will be run together, with nothing inbetween them.
Naturally, that won't work once the runs may be interleaved.

@google-cla google-cla bot added the cla: yes label Jun 3, 2021
@LebedevRI LebedevRI requested a review from dmah42 June 3, 2021 07:48
While the current variant works, it assumes that all the instances of
a single family will be run together, with nothing inbetween them.
Naturally, that won't work once the runs may be interleaved.
@LebedevRI LebedevRI force-pushed the per-family-complexity-reports branch from e8e2471 to 89adc8e Compare June 3, 2021 08:06
@LebedevRI
Copy link
Copy Markdown
Collaborator Author

@dominichamon does this look good to you now?

@LebedevRI LebedevRI merged commit 0c1da0a into google:main Jun 3, 2021
@LebedevRI LebedevRI deleted the per-family-complexity-reports branch June 3, 2021 08:46
vincenzopalazzo pushed a commit to vincenzopalazzo/benchmark that referenced this pull request Feb 8, 2022
While the current variant works, it assumes that all the instances of
a single family will be run together, with nothing inbetween them.
Naturally, that won't work once the runs may be interleaved.
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.

2 participants