Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

New Version is 14x slower then the one with the torchao error

Open
#1,007 8 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
python, pytorch

Research direction

The report compares two ai-toolkit versions on identical Windows/5070ti hardware, claiming the only differences are the torchao error and the toolkit version; it names no file, log or reproduction command. Start by finding where torchao and the training loop's optimization path are configured, then diff the reporter's version against current main to bisect the slowdown. Done means an identified commit or config change plus repeated step-time measurements on the same setup confirming the regression.

Written by the indexing model from the issue text.

Description

This is for bugs only

Did you already ask in the discord?

No and never will (I am boycotting discord, and you should too)

You verified that this is a bug and not a feature request or question by asking in the discord?

Yes

Describe the bug

I mean how?

Version With Torchao Error
HR_Krea2: 19%|#9 | 501/2600 [00:21<12:24:06, 21.27s/it, lr: 9.2e-05 loss: 6.988e-02]

Latest version:
HR_Krea2: 19%|#9 | 501/2600 [05:03<177:04:17, 303.70s/it, lr: 9.3e-05 loss: 1.196e-01]

Beside the torchao and AI-Toolkit version, the environment is exactly the same. Windows/5070ti.

Name: torch
Version: 2.13.0+cu130
Name: torchvision
Version: 0.28.0+cu130

Dominant language
Python
Stars
12.2k
Forks
1.6k
Avg merge
1m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ostris/ai-toolkit

All issues in ostris/ai-toolkit

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.