drop-tracy-from-ci #16857
Closed
drop-tracy-from-ci #16857
Conversation
This file contains 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
Abbreviated Benchmark Summary@ commit 9e2d01fb0f82a4eadfaad6457b2e1c4c9f7190a5 (vs. base 767a6112abffebd896ceb2f0107c0d603c2a338a) Data-Tiling Comparison TableClick to show
Improved Latencies 🎉
[Top 3 out of 13 results showed] No improved or regressed compilation metrics 🏖️ For more information: |
ScottTodd
added a commit
that referenced
this pull request
May 14, 2024
This drops support for capturing traces as part of CI benchmarking to fix #16856. This PR is a synced and updated version of #16857. While traces are invaluable in analyzing performance, * This implementation is difficult to maintain (updating IREE's Tracy version can't be performed without also building for multiple operating systems and uploading binary files to a cloud bucket with limited permissions) * Trace collection nearly doubles CI time for every benchmark run (i.e. 10m->20m or 20m->40m), leading to occasionally long queueing (2h+) * Trace collection contributes to cloud storage and network usage (there are larger offenders: #16396, but we still need to trim costs) --------- Co-authored-by: Benoit Jacob <jacob.benoit.1@gmail.com>
bangtianliu
pushed a commit
to bangtianliu/iree
that referenced
this pull request
Jun 5, 2024
This drops support for capturing traces as part of CI benchmarking to fix iree-org#16856. This PR is a synced and updated version of iree-org#16857. While traces are invaluable in analyzing performance, * This implementation is difficult to maintain (updating IREE's Tracy version can't be performed without also building for multiple operating systems and uploading binary files to a cloud bucket with limited permissions) * Trace collection nearly doubles CI time for every benchmark run (i.e. 10m->20m or 20m->40m), leading to occasionally long queueing (2h+) * Trace collection contributes to cloud storage and network usage (there are larger offenders: iree-org#16396, but we still need to trim costs) --------- Co-authored-by: Benoit Jacob <jacob.benoit.1@gmail.com>
LLITCHEV
pushed a commit
to LLITCHEV/iree
that referenced
this pull request
Jul 30, 2024
This drops support for capturing traces as part of CI benchmarking to fix iree-org#16856. This PR is a synced and updated version of iree-org#16857. While traces are invaluable in analyzing performance, * This implementation is difficult to maintain (updating IREE's Tracy version can't be performed without also building for multiple operating systems and uploading binary files to a cloud bucket with limited permissions) * Trace collection nearly doubles CI time for every benchmark run (i.e. 10m->20m or 20m->40m), leading to occasionally long queueing (2h+) * Trace collection contributes to cloud storage and network usage (there are larger offenders: iree-org#16396, but we still need to trim costs) --------- Co-authored-by: Benoit Jacob <jacob.benoit.1@gmail.com> Signed-off-by: Lubo Litchev <lubol@google.com>
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.
No description provided.