Jira (PUP-10719) Puppet's feature detection can leave rubygems in a bad state

[Josh Cooper (Jira)]

Title: Message Title

Josh Cooper commented on PUP-10719   Re: Puppet's feature detection can leave rubygems in a bad state Interestingly, the feature that enables puppet to load extensions from gems causes the number of file I/O operations to increase by ~2.5 times during catalog compilation using the pupetserver perf control repo. Seems completely unnecessary for the rubygems cache to be cleared during compilation. [root@unheeded-statue ~]# strace -e trace=file -o trace.log -- puppet catalog compile -E perf_control > /dev/null [root@unheeded-statue ~]# grep /opt/puppetlabs/puppet/lib/ruby/gems/2.5.0 trace.log | wc -l 13743 [root@unheeded-statue ~]# strace -e trace=file -o trace-nogems.log -- puppet catalog compile -E perf_control > /dev/null ... [root@unheeded-statue ~]# grep /opt/puppetlabs/puppet/lib/ruby/gems/2.5.0 trace-nogems.log | wc -l 5518 Add Comment   This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374990.1602706184000.56185.1602720840032%40Atlassian.JIRA.