Markus Roberts a écrit :
Aurelien --
Thank you!
I noticed that the time needed by puppetd to write on disk its
cached catalog has increased a lot in Puppet 0.25.
I'm using 0.25.4 and, with a catalog with around:
~400 resources: i need 3 sec to write this on disk
~900 resources: i need 8 sec
~1900 resources: i need 21 sec.
So slow and getting slower (though the r^2 term is ~0.001, so it's not
the dominating factor at this point). Can you describe your test setup
in a bit more detail?
We noticed this problem doing some scalability check for our current
configuration.
I tried to reproduce the problem. I put aside one of our machine.
I disabled its current configuration, and replace it by a simple
node foo {
import "foo.pp"
}
# for i in {1..900}; do echo "file { '/tmp/foo$i': content => 'foo'; }"; done >
foo.pp
And I ran puppetd -t --debug on this node.
If you watch for the time needed to fetch and backup the catalog. You will see
this is very long.
I noticed the problem is limited to the work needed to write the catalog on
disk.
It should be easy to reproduce this in your environment.
I do not reproduce this issue with Puppet 0.24.
Meaning, I assume, that it was not noticeably slow or that you were
unable to measure it?
It is not slow (in fact, it is even really quick).
Time needed to write several dozen of kilobytes should not be above 1 sec, at
most.
And, again, thank you for taking the time to do these measurements; it's
quite helpful as we prepare to roll out 2.6 to get feedback on where we
are going in the right or wrong direction historically.
I imagine you mean 0.26 ? :)
--
Aurelien Degremont
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" 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-dev?hl=en.
