Google Git
Sign in
opensecura / 3p / openxla / iree / 2eea916a777947ef4162a2aa44f47a2c6c1fb926
commit2eea916a777947ef4162a2aa44f47a2c6c1fb926[log] [tgz]
authorScott Todd <scott.todd0@gmail.com>Mon Jul 15 14:59:50 2024 -0700
committerGitHub <noreply@github.com>Mon Jul 15 14:59:50 2024 -0700
tree4b05a98df06cad7856b80042a84df8e6171a878d
parentf89a7da8b8671c20ea8a0f87a416de49b087b0eb [diff]
Disable Android benchmarks while device is offline. (#17910)

We have two pixel-6-pro devices/runners, one labeled for `presubmit` one
labeled for `postsubmit`. The presubmit runner has been offline for
multiple days, causing benchmark runs on LLVM integrate PRs to time out
waiting for a runner (and blocking other benchmark results from getting
reported as PR comments).

Some options:
* https://github.com/iree-org/iree/pull/17896 
* Switch only Android presubmit benchmarks to also use postsubmit
benchmark runners
* Turn off Android benchmarks on presubmit (or just for LLVM integrate
PRs)
* Switch benchmarks from pixel-6-pro to pixel-8-pro (we tried this
before but pixel 6 was more stable than pixel 8... I'm not sure how much
that level of stability is useful at this stage though, need to keep
rolling forward with testing on recent hardware)
* (THIS PR) Turn off Android benchmarks entirely

See also [this discussion on
Discord](https://discord.com/channels/689900678990135345/1080178290188374049/1260359410035724402).

benchmark-extra: default
1 file changed
tree: 4b05a98df06cad7856b80042a84df8e6171a878d
  1. .github/
  2. build_tools/
  3. compiler/
  4. docs/
  5. experimental/
  6. integrations/
  7. lib/
  8. llvm-external-projects/
  9. runtime/
  10. samples/
  11. tests/
  12. third_party/
  13. tools/
  14. .bazel_to_cmake.cfg.py
  15. .bazelignore
  16. .bazelrc
  17. .bazelversion
  18. .clang-format
  19. .dockerignore
  20. .git-blame-ignore-revs
  21. .gitattributes
  22. .gitignore
  23. .gitmodules
  24. .pre-commit-config.yaml
  25. .yamllint.yml
  26. AUTHORS
  27. BUILD.bazel
  28. CITATION.cff
  29. CMakeLists.txt
  30. configure_bazel.py
  31. CONTRIBUTING.md
  32. LICENSE
  33. MAINTAINERS.md
  34. README.md
  35. RELEASING.md
  36. WORKSPACE
README.md

IREE: Intermediate Representation Execution Environment

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.

CI Status IREE Discord Status

Project Status

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!

Communication Channels

Related Project Channels

  • MLIR topic within LLVM Discourse: IREE is enabled by and heavily relies on MLIR. IREE sometimes is referred to in certain MLIR discussions. Useful if you are also interested in MLIR evolution.

Architecture Overview

IREE Architecture IREE Architecture

See our website for more information.

Presentations and Talks

Community meeting recordings: IREE YouTube channel

  • 2021-06-09: IREE Runtime Design Tech Talk (recording and slides)
  • 2020-08-20: IREE CodeGen: MLIR Open Design Meeting Presentation (recording and slides)
  • 2020-03-18: Interactive HAL IR Walkthrough (recording)
  • 2020-01-31: End-to-end MLIR Workflow in IREE: MLIR Open Design Meeting Presentation (recording and slides)

License

IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.