In .venv/lib/python3.10/site-packages/torch/_inductor there is this utils file.
The utils file basically keeps track of what GPU/CPU is currently running the main script for the sake of Torchrun.
I have a laptop with 3050TI, Cuda toolkit installed both in my windows, and my wsl. I am updating my driver.
In order to run the script runs/speedrun.sh after I made the changes to it so that it runs with 1 gpu in mind and is at 8 Size I must be in the wsl envrionment which is currently set to ubuntu 22.04.
While running it pitches the fault that Not enough SM to run MAX_AUTOTUNE_GMM. and then just stops there.
This is immediately after it basically tells me how many flops it would need to perform the tune, and the size of each batch.
I had antigravity set all torch.compile(mode=default) and it still had the same issue, since it's a prompt and it just haults the process entirely.
It even loads cuda when initiating the script, its several of the 81 dependencies it installs when it recreates the virtual environment.
I'm confused what to do here, since I did remove all torchrun and set the gpu=1 and batch_size=8. It just won't do anything.
Is it that I'm running it in wsl? I have tried in python and in base windows, and they both just don't work since the commands are just not supported.
Much appreciated for your response.
Also, most the windows repos in these forks have the same issues, they don't get past this issue.
In .venv/lib/python3.10/site-packages/torch/_inductor there is this utils file.
The utils file basically keeps track of what GPU/CPU is currently running the main script for the sake of Torchrun.
I have a laptop with 3050TI, Cuda toolkit installed both in my windows, and my wsl. I am updating my driver.
In order to run the script runs/speedrun.sh after I made the changes to it so that it runs with 1 gpu in mind and is at 8 Size I must be in the wsl envrionment which is currently set to ubuntu 22.04.
While running it pitches the fault that Not enough SM to run MAX_AUTOTUNE_GMM. and then just stops there.
This is immediately after it basically tells me how many flops it would need to perform the tune, and the size of each batch.
I had antigravity set all torch.compile(mode=default) and it still had the same issue, since it's a prompt and it just haults the process entirely.
It even loads cuda when initiating the script, its several of the 81 dependencies it installs when it recreates the virtual environment.
I'm confused what to do here, since I did remove all torchrun and set the gpu=1 and batch_size=8. It just won't do anything.
Is it that I'm running it in wsl? I have tried in python and in base windows, and they both just don't work since the commands are just not supported.
Much appreciated for your response.
Also, most the windows repos in these forks have the same issues, they don't get past this issue.