Jira (FACT-635) Facter is very slow when large number of network interfaces exist

[Clayton O'Neill (JIRA)]

Title: Message Title

Clayton O'Neill commented on an issue   Re: Facter is very slow when large number of network interfaces exist I think instead of 4, it might be worthwhile to consider pulling the data directly from /sys/class/net/. I think this is at least as stable of an interface as ifconfig is and it's dramatically faster. On the same system, Ansible can gather facts in about 12 minutes, vs 75+ for facter. More details on their implementation can be found here: https://github.com/ansible/ansible/blob/devel/lib/ansible/module_utils/facts.py#L1510-L1563 Add Comment   Facter / FACT-635 Facter is very slow when large number of network interfaces exist We ran into this on an OpenStack control node that has a very large number of interfaces (1300+), most of which are tap interfaces for Open vSwitch. Because facter runs ifconfig/ip/etc for every interface found, and that takes 100-200ms per interface, this means that a facter run can take over an hour. I'd prepose that the fix for this would be to ign... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.