I thought the same, until I noticed a really annoying WSL2 bug: On two machines I own, waking up from hibernate or standby causes a wsl related process (vmmem) to consume 100% CPU, with wsl becoming completely unresponsive (including wsl terminate etc).
You have to kill all wsl processes, which requires admin rights. So without elevated rights, Ubuntu on windows is not usable on these laptops.
I ran into this issue as well. I also spent a few hours debugging problems with a database just to discover that I could not reach a server because WSL2 does not support IPV6 (https://github.com/microsoft/WSL/issues/4518)
There is a typo in the in app purchase page: "unlimmited"
I clicked on one story, did not like it, so i canceled it. I wanted to give the app a second chance. But alas, only one story is allowed per day.. Maybe increase this at least for the first day or do not count unfinished stories....
So the code looks (apart from pointers) similiar to numba which feels much closer to numpy/pytorch high level code. Are there huge advantages in the triton model compared to numba that I don't see? Or is there a big performance gap?
For me numba was always the easiest way to get some new idea running on cuda, and most of the time it was fast enough..
Did anybody find performance comparison between numba and triton?
Unlike Numba, Triton operators operate on blocks with explicit load and store of blocks. This is what enables analysis to automate coalescing, shared memory management, etc.
I guess Triton is not for you if Numba is fast enough.
reply