Adding a profiling page #91
Conversation
src/contrib/profiling-sssd.rst
Outdated
| $ sudo apt install linux-tools-common linux-tools-generic | ||
|
|
||
|
|
||
| Make sure SSSD's and its dependencies' debug information is available, either |
There was a problem hiding this comment.
Sounds strange,
`Make sure SSSD and debugging are working by issuing debuginfod. Otherwise, ensure all necessary debug packages are installed.
src/contrib/profiling-sssd.rst
Outdated
|
|
||
| .. note:: | ||
|
|
||
| It is possible that SELinux prevents ``perf`` from monitoring your process. |
There was a problem hiding this comment.
Is this certain? That SELinux rules block perf from interacting with the SSSD domain? If it's for certain, then we should phrase it that way.
The shipped targetted SELinux policy will prevent ``perf`` from interacting with the SSSD process. You can look at the audit logs or put SELinux into permissive mode to confirm. You will need to add additional rules and can be done using ``audit2allow``.
There was a problem hiding this comment.
I slightly modified it as this text is meant for any distribution, not only RHEL or Fedora (although the given examples are for Fedora and Ubuntu). How does it look?
| to the process while it is running. | ||
|
|
||
| Once SSSD is running and ready to be profiled, identify the PID of the process | ||
| you want to monitor (``sssd_ssh``, ``sssd_nss``, ``sssd_be``, etc.), start the |
There was a problem hiding this comment.
It would be nice to provide more examples, as in what data will be profiled selected the common processes. We will make the assumption that administrators may fully understand the SSSD architecture.
There was a problem hiding this comment.
Added one more example.
|
Fixed the comments and also some small errors I found. |
Adding a page describing how to profile any of the SSSD daemons.
The page be seen here: https://sssdio--91.org.readthedocs.build/contrib/profiling-sssd.html