Daniel Pittman a écrit :
It would be great to improve that, from our point of view, but I
wonder a bit: when is this a killer problem for everyone?
Also, someone commented about using marshall to speed this up - sadly,
that isn't an acceptable solution. We have had problems with Marshall
data being impossible to transport between Ruby versions, and worse,
causing segfaults. That means we can't use it to persist data where
it might be read by a different version Ruby later.
Caching catalog may not be used as a cache. We are using puppet only in
interactive mode and we use the cache to extract some data (like a kind
of report).
So if the cache doesn't pass the ruby upgrades or if it make sometime a
segfault
(does it ever happened to me for now) it's does not matter. On the other
side, win
some seconds is much appreciated.
Émile
--
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.
