It's pure client-side JS — no backend, no tracking, no signup. The math lives in formulas.js so you can sanity-check it against the CUDA Programming Guide. Architectures and their per-SM limits are in presets.js.
Things I'd love feedback on:
* Are the per-arch limits correct for [arch you're least sure about]?
* The "compare two configs side-by-side" view - is the diff readable?
* Anything you wish the Excel version did that this doesn't?
Link: https://toolbelt.widgita.xyz/cuda-occupancy-calculator/
(There are a few other small tools at the root, but this one is the reason for the post.)
leninkatta•34m ago