4 ms·
Of course they cause problems as well, you not believing it doesn't change profiler facts. I can also easily point you on CppCon, C++Now and WWDC talks, where
by pjmlp 6mo ago
Of course they cause problems as well, you not believing it doesn't change profiler facts.
I can also easily point you on CppCon, C++Now and WWDC talks, where presenters spend valuable time of their lifes speaking about matters you don't believe.
- antiloper 6mo agoCan I see the profiler data that shows AddRef/Release being a performance bottleneck?
- pjmlp 6mo agoYes, learn to use one and point it to a C++ Github project full of shared pointers.
- CJefferson 6mo agoI don’t believe it’s Limiting factor in UI frameworks. I’ve profiled a lot of c++ and a lot of UI code. UI problems tend to come from too much churn and object creation, or doing too much work in the UI thread so it gets laggy, not just doing some reference counting.
- antiloper 6mo agoembarrassing
- coffeeaddict1 6mo agoWhile I agree that shared pointer are problematic (I almost never use them in C++), I don't think they're ever really the reason for performance issues in GUI apps. I've been doing GUI programming for more than a decade now and the overwhelming majority GUI performance issues come down to issues like poor use of concurrency (blocking GUI thread), unoptimised algorithms (e.g. for layouts), overdrawing, GPU/CPU sync issues or inefficient input handling. I have never encountered a performance issue that was to due to reference counting (in fact I'm a big user of the CoW idiom when it comes to UI).
- pjmlp 6mo agoWhich of those GUIs have you used where everything was a COM element?