List view
- No due date
- No due date•2/2 issues closed
- No due date•5/6 issues closed
- Due by February 28, 2026
Captures work related to deployment, SLURM scheduling, topology scheduling for 36xBH GLX
Due by March 31, 2026•1/3 issues closed- Due by March 31, 2026•1/2 issues closed
- Overdue by 17 day(s)•Due by January 30, 2026•22/25 issues closed
- Overdue by 16 day(s)•Due by January 31, 2026•3/3 issues closed
Tracking baseline "zero-load" Fabric performance characterization for BH Galaxy Pod. Tested on 8x16 and 4x32 pods. zero-load latency, various bandwidth traffic patterns x all topologies
Overdue by 10 day(s)•Due by February 6, 2026•8/16 issues closedCatch all milestone for quality of life improvements
Due by March 31, 2026•0/2 issues closed- No due date•0/1 issues closed
On completion of this milestone, all initial fabric manager + fabric control paths are expected to be complete. This means: - Fabric manager has control flows with fabric, allowing it to pause, resume, exit, issue retrain - Fabric is expected to always respond to the above messages (barring chip failure or noc hangs)
Overdue by 10 day(s)•Due by February 6, 2026•2/7 issues closedPerformance workitems scheduled for large LLM inference. Includes low-latency work for low-latency decode and other miscelaneous optimizations to bump up 2D perf to near linear fabric levels.
Overdue by 3 day(s)•Due by February 13, 2026•6/29 issues closed- No due date•3/15 issues closed
Time to do more model work with TTT (v1 and v2)!
No due date•1/6 issues closed- Overdue by 12 day(s)•Due by February 4, 2026•13/20 issues closed
- Overdue by 5 day(s)•Due by February 11, 2026•3/16 issues closed
- Due by February 20, 2026•5/13 issues closed
- Due by March 31, 2026•0/1 issues closed
- Due by March 29, 2026
The first minor release of TTTv2 [!NOTE] > MINOR (second digit) > New features added, but old features/APIs still work exactly the same. > No breaking interface changes allowed.
No due date•0/16 issues closed- Due by February 28, 2026•14/31 issues closed
- Overdue by 1 month(s)•Due by December 23, 2025•14/16 issues closed
- Overdue by 2 month(s)•Due by December 15, 2025•27/29 issues closed
- No due date•46/49 issues closed
- No due date•5/11 issues closed
- No due date•12/23 issues closed
- No due date•4/12 issues closed
- Overdue by 1 month(s)•Due by December 22, 2025•3/5 issues closed
- Overdue by 2 month(s)•Due by December 15, 2025•1/1 issues closed
- Overdue by 2 month(s)•Due by November 24, 2025•1/1 issues closed
- Overdue by 3 month(s)•Due by October 31, 2025•2/2 issues closed
- Overdue by 4 month(s)•Due by September 29, 2025•1/1 issues closed
- Overdue by 4 month(s)•Due by September 22, 2025•1/1 issues closed
This milestone is for all of the issues that are research and development into NOC HW features that exist, and should have proper writeups and documentation
No due date•12/16 issues closeddata_movement infrastructure has some issues that can be fixed and refactored to allow for more scalability and easier additions
Overdue by 4 month(s)•Due by September 30, 2025•13/15 issues closedCleanup op-facing APIs + HW APIs for data movement, and re-factor or remove APIs when necessary
Overdue by 4 month(s)•Due by September 30, 2025•7/12 issues closed- No due date•3/3 issues closed
The focus is to scale-up to a bigger mesh across multiple hosts. 1. Enable Multi-Host Metal/Fabric u-Benchmarks on 2x Galaxy 2. Enable Metal Support for Emulated and Physical Multi-Host Testing 3. Enable Preliminary Support for Developers to write Multi-Host Ops, and end-to-end model tests
Overdue by 7 month(s)•Due by June 30, 2025•17/17 issues closedAdd tests in the data_movement folder for P1 ops & patterns
Overdue by 4 month(s)•Due by September 30, 2025•15/19 issues closedAdding tests in the data_movement folder for P0 primitives, and also P0 ops
Overdue by 5 month(s)•Due by August 31, 2025•22/24 issues closedImproving docker experience, features w/ the repo, bugs, and build / use efficiency
No due date•9/10 issues closedThis is a catch-all for all tickets in the 2025-Q1 effort to get the Metal CI to Green Acceptance criteria: - On a weekly average, 90% of All-Post-Commit's (or its successor's) runs are green, under the criteria described here: https://superset.tenstorrent.com/superset/dashboard/54/
No due date•20/23 issues closed- No due date•16/16 issues closed
Work to improve syseng releases (tt-kmd, fw, flash,etc) processes. Acceptence Criteria: Firmware releases are communicated effectively to Metal team Firmware releases are tested on Metal-supplied tests before release Firmware releases are released in an incremental an automated way such that Metal can test and intake as appropriate
No due date•3/6 issues closedBuild/Test/Deliver Metalium on Ubuntu 22.04
No due date•6/7 issues closed- No due date•4/4 issues closed
This set of issues will detail how we can optimize CI build and test before the wave of new hires show at the beginning of next year. We only have so many machines and boards and need to start being more efficient via incremental builds and testing.
Overdue by 1 year(s)•Due by January 1, 2025•1/2 issues closed- No due date•10/10 issues closed
This milestone is for tracking progress of building and testing Metal in Ubuntu 22.04/24.04 docker and native OS.
No due date•18/18 issues closed