Drop Tracy from CI benchmarks. (#17383) This drops support for capturing traces as part of CI benchmarking to fix https://github.com/iree-org/iree/issues/16856. This PR is a synced and updated version of https://github.com/iree-org/iree/pull/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: https://github.com/iree-org/iree/issues/16396, but we still need to trim costs) --------- Co-authored-by: Benoit Jacob <jacob.benoit.1@gmail.com>
IREE (Intermediate Representation Execution Environment, pronounced as “eerie”) is an MLIR-based end-to-end compiler and runtime that lowers Machine Learning (ML) models to a unified IR that scales up to meet the needs of the datacenter and down to satisfy the constraints and special considerations of mobile and edge deployments.
See our website for project details, user guides, and instructions on building from source.
IREE is still in its early phase. We have settled down on the overarching infrastructure and are actively improving various software components as well as project logistics. It is still quite far from ready for everyday use and is made available without any support at the moment. With that said, we welcome any kind of feedback on any communication channels!
See our website for more information.
Community meeting recordings: IREE YouTube channel
IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.