On 7/6/22 08:42, Michael Catanzaro wrote:
On Wed, Jul 6 2022 at 04:20:50 PM +0100, Jonathan Wakely <jwakely@xxxxxxxxxx> wrote:
You build locally and profile using your locally built packages.
Problem is that in order to get good profiling results today, you need to rebuild all dependencies with frame pointers enabled. And that is not realistic. Nobody does that.
Developers normally only build what they are working on, not 100 dependencies including mesa, glibc, etc.
With the current profiling methods, are you able to at least narrow down which libraries
applications spend the most time in? Or do you really need detailed profile information for
every single library in order to determine where the problem is?
-Tom
Michael
_______________________________________________
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
_______________________________________________
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
