On Thu, Jul 07, 2022 at 08:13:52PM -0000, Christian Hergert wrote: > Sysprof has modular data collection backends, and not everything > requires linking against libunwind. > > For those not familiar with Sysprof, or profiling the desktop at > large, generally a single program is not the problem. The performance > problems often exist across a number of processes. That can be anything > from a library used by multiple applications which cumulatively waste > resources, IPC across programs, thundering herds when files on disk > change, GPU usage, CPU frequency scaling, memory bandwidth, RAPL, etc. That problem's not unique to the desktop space, it applies across any non-trivial usage of the OS, whether down at the base infrastructure level, or over at server applications too. IOW, don't think of 'sysprof' as only a tool for the desktop developers, what you describe is broadly applicable to any and all. Profiling on Linux is indeed an exercise in frustration much of the time, and recently I find myself turning to sysprof more than other options for analysing problems around the virt stack. With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
