pytorch/ao

PyTorch native quantization for training and inference

Hosted by PyTorch Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

pytorch/ao has 3k+ stars and 650+ forks on GitHub, is written in Python, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 11th, 2026
Created on November 3rd, 2023
Open Issues & Pull Requests: 815 (+0)
GitHub issues: Enabled
Number of forks: 655
Total Stargazers: 3,005 (+0)
Total Subscribers: 44 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.2 hours
Mean response time: 33.6 days
90th percentile: 27.9 days
Tracked items: 733

Maintainer activity

22 people did triage or write work on this repository in the last 12 months.

At least 23% of ao's 22 maintainers work at Meta. 13 say where they work, and 5 of those are Meta.

PyTorch Foundation owns this repository. 1 of its person did this work here, and is not included above.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 17% of issues opened in the past year have never received a reply. 96% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 69% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 44% of issues opened in the past year have been closed. Three people close 56% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 300
New in 7 days: 5
Closed in 7 days: 4
Avg open age: 337 days
Stale 30+ days: 281
Stale 90+ days: 239

Recent activity

Opened in 7 days: 5
Closed in 7 days: 4
Comments in 7 days: 20
Events in 7 days: 32

Top labels

  • triaged (110)
  • bug (62)
  • float8 (50)
  • good first issue (48)
  • tracker (38)
  • mx (33)
  • enhancement (29)
  • quantize_ (26)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

TorchAO is a PyTorch native quantization library that optimizes models for both training and inference through techniques including float8 quantization, int4 quantization, and sparsity.

The library addresses the challenge of reducing model size and computational cost while maintaining accuracy during both training and serving phases. It provides quantization-aware training to recover accuracy lost during quantization, float8 training to accelerate pre-training workloads, and post-training quantization for inference optimization. The tool integrates directly with PyTorch's native operations, allowing developers to apply these optimizations without leaving the PyTorch ecosystem.

Developers should choose this tool if they are working with large language models or transformer architectures and need to optimize for either training speed or inference efficiency. It suits projects where reducing memory footprint and latency are critical, particularly when fine-tuning or serving models like Llama or Gemma. The library is designed for practitioners who want production-ready quantization without complex external dependencies, as it leverages PyTorch's native capabilities.

The project shows active development with recent integrations into complementary tools and ongoing work on specialized techniques like mixture-of-experts training optimization. Contributors are actively expanding the library's scope to cover emerging model architectures and training scenarios, as evidenced by prototype implementations for new quantization methods. The team maintains comprehensive documentation and makes quantized model checkpoints and training recipes publicly available, indicating a commitment to reproducibility and practical usability.