60 minutes is still too high for managing 8k change events that won't
ever match (or be used in the end) :-(
+1
It's certainly better (in time) to what it would be without the patch
(ie do you have this number, assuming the server is not swapping)?
yes, I think that might be the best explanation.
I think we need a smarter way of matching those events, something
involving pruning the graph of some sort. I'll try to think about this.
Thanks! I'm happy to test anything you bring up. Unfortunately I don't
have enough time to support you in finding an appropriate proposal.
To be clear: this is really only a problem within the first run when
puppet touches _every_ file. If it has to touch only a few files it
finishes much faster. For example in about 7 minutes to fix 1k of
files. Which means imho that the main problem remains in passing the
events up.
Still regarding the features and advantages you get by chown/chmoding
such a structure with puppet resources, it would be great if that
could be passed in a reasonable amount of time.
The problem is not only for chown/chmoding. It just means we are
inefficient at managing many events (granted there might not be too many
real situation generating that many events).
yes.
cheers pete
--
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.
