Issue #7959 has been updated by Dominic Cleal.
Keywords set to augeas
Type checking is performed by the Augeas library itself. Puppet simply allows
you to flip the flag on and off, so I think this is more of an upstream issue.
The src/augeas.h comments say "since it can be very expensive it is not done by
default". You can see this just from running augtool with type checking
enabled:
$ /usr/bin/time augtool -c quit
55.34user 1.36system 0:57.23elapsed 99%CPU (0avgtext+0avgdata
786044maxresident)k
0inputs+0outputs (0major+773569minor)pagefaults 0swaps
It's using up to 767MB to type check every lens and takes nearly a minute!
As the type checking will be performed for every lens loaded, then you're
creating a lot of work for the library. I'd suggest you use the Puppet type's
lens/incl attributes to reduce the workload to a single lens and see if that
improves matters for you.
----------------------------------------
Bug #7959: augeas type_check RAM usage
https://projects.puppetlabs.com/issues/7959
Author: Markus Falb
Status: Unreviewed
Priority: Normal
Assignee:
Category: agent
Target version:
Affected Puppet version:
Keywords: augeas
Branch:
augeas { "ram fresser":
type_check => true,
context => "/files/etc/sysctl.conf",
changes => "set net.ipv4.ip_forward 1",
}
and puppet needs 1GB RAM ? This looks wrong to me. I only see this behaviour if
type_check is true.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
