We're going to be refreshing Superluminal's website this year. We have a pretty good idea of what to change, but I'm curious —
In your own words, if you're using Superluminal, why do you like using it?
=> More informations about this toot | More toots from rovarma@mastodon.gamedev.place
@rovarma Because it is dead simple to use and get running, and it immediately shows me the biggest culprits in terms of lost performance or stalls.
=> More informations about this toot | More toots from molecularmusing@mastodon.gamedev.place
@rovarma it’s the quickest way that I can find slow code and make it not slow. I find the easy access to the disassembly view of slow code makes it phenomenally powerful for working out what I or the compiler did wrong and how to fix it.
=> More informations about this toot | More toots from neilhenning@mastodon.gamedev.place
@rovarma it is plain and utter simple (even led me to lose a job due to its clarity 😅), unsure if you have added DWARF support on Windows but that would be a big plus at my current place
=> More informations about this toot | More toots from crystalmoon@chaos.social
@crystalmoon there’s no dwarf support on windows currently, but it will most likely come along with the Linux support
even led me to lose a job due to its clarity
sorry to hear that! but also, tell me more! 🙈
=> More informations about this toot | More toots from rovarma@mastodon.gamedev.place
@rovarma 0 friction. It sometimes takes me literally 5 minutes from capturing the profile to pinpointing the problem
=> More informations about this toot | More toots from msinilo@mastodon.gamedev.place
@rovarma because it is fastest way from “oh I wonder what’s going on here” to “oh shit, it is this!”
=> More informations about this toot | More toots from aras@mastodon.gamedev.place
@rovarma also curiously, but maybe not that surprisingly, I'm sometimes using Superluminal to learn about how some piece of code works. Capture the run, and then I can see what calls what, in which order things happen, etc. Things higher up provide broad overview, and can drill down into what happens at leaf levels.
=> More informations about this toot | More toots from aras@mastodon.gamedev.place
@aras @rovarma same! this is how I figured out what things like Qt were doing since the callback setup was hard to reason about directly
=> More informations about this toot | More toots from superfunc@mastodon.gamedev.place
@aras @rovarma Telling you how things are connected in a program is an essential feature of a profiler!
=> More informations about this toot | More toots from wolfpld@mastodon.gamedev.place
@wolfpld @aras @rovarma profilers are the programmer's x-ray machines
=> More informations about this toot | More toots from sschoener@mastodon.gamedev.place
@rovarma
✔ Reliable
✔ No integration needed
✔ Great UI
✔ Feels bloat-free
✔ Fairly priced personal license
=> More informations about this toot | More toots from agersant@mastodon.gamedev.place
@rovarma zero setup, zero friction, amazing support. Made by people who obviously use their own tools and underatand what "user pain" is. Gives you the information you actually want out of VTune 99% of the time except it doesn't crash, doesn't hang, doesn't take ages.
=> More informations about this toot | More toots from sschoener@mastodon.gamedev.place
@rovarma In my experience it's the only profiler out there, that actually "just works". I didn't even read the manual. Never had this happen with this type of software, ever.
=> More informations about this toot | More toots from LarsThiessen@mastodon.gamedev.place This content has been proxied by September (3851b).Proxy Information
text/gemini