Pyrek Paweł
Aras PranckevičiusMy #bcon24 talk "How to accidentally start working on Blender VSE" is up: slides https://aras-p.info/texts/img/2024-bcon-vse.pdf and video https://www.youtube.com/watch?v=WJVQLpGHB8g
Josh Simmons@aras random note, but incase anybody watching is unsure, I would say on Linux these days if you want to do casual profiling the best answer is samply! at least until we get superluminal support. https://github.com/mstange/samply
fysx
@fysx @aras Yep, though tracy requires a lot more setup before you're getting useful data, so it's less of a casual option. The core advantage of (something like) samply is you type `samply record blender` and voila you're off to the races. When you close blender it'll open a browser window with the resulting profile.
@dotstdy cool, thanks!
Sebastian Schöner@aras great talk. Using a profiler is a good idea not just for seeing perf but also to get a high level overview of what is happening: A good profiler is like an x-ray machine, it lets you see right through everything and see the skeleton that holds the process together.
@sschoener yeah indeed. Forgot to mention that aspect! Browsing a flame chart not because you’re looking for a problem, but just because I want to see what happens in what order is very useful.
@aras @sschoener It's often even better in a tracing profiler too, since then you can annotate functions with data values. You end up with a souped up gui version of printf-debugging. (ofc that's harder to get without the profiler actually being properly integrated in the application)
Michael Knudsen@aras lots of good points.
I've realised I keep coming back to the word 'intent' when writing code comments, commit messages, and PRs.
Most often, the why matters a lot more than the how and what.
People may have written their code perfectly, but if what they are trying to achieve is completely misguided comments are often useless.
@aras btw. was hoping that you'd say your name to se if my idea of its pronunciation is any good. (: