* Jason L. Tibbitts, III: >>>>>> Neal Gompa <ngompa13@xxxxxxxxx> writes: > >> The problem is that policy modules can depend on each other, and since >> policy modules can add things both to the global store and to the pool >> of stuff other modules can use, it has to be processed serially. > > Even then, semodule itself takes a surprising amount of time to run. > Whether it is faster or slower than the full restorecon run depends > quite a bit on how much data the system has. I do wonder if there's any > way to make it even a little less glacial. Yes, it seems quite malloc-heavy. Switching from bzip2 to zstd could help a bit, too. In the past, regular expression compilation using PCRE was a major bottleneck, but I didn't see that during the last updates. Thanks, Florian -- _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
