The selmodule provider ends up calling /usr/sbin/semodule --list one or twice per resource. This results in a heavy duplication of effort and increased apply time. By implementing a cache, apply times drop 80% or more.
The {{selmodule}} provider ends up calling {{/usr/sbin/semodule --list}} one or twice _per_ resource. This results in a heavy duplication of effort and increased apply time. By implementing a cache, apply times drop 80 50% or more.
Improved performance on the selmodule provider The `selmodule` provider was calling `/usr/sbin/semodule —list` one or twice per resource. This results in a heavy duplication of effort and increased apply time. Thanks https://github.com/montaguethomas for for implementing a cache which improves the performance.