Hello
Hmmm... I missed that cached format in not using preferred_serialization_format
value...
This is YAML whatever I put there.
So this is the issue... YAML serialization for catalog is slow, and there is no
way to work around this.
In 0.24, catalog_format was used there. So there is a regression here.
Do you have workarounds or patches for this ?
Thanks
Brice Figureau a écrit :
On Mon, 2010-06-28 at 17:44 +0200, Aurelien Degremont wrote:
R.I.Pienaar a écrit :
I might be wrong, but at the moment we take a PSON encoded catelog from the
master, decode it, then recode it into YAML and save it to disk?
I think I recall a ticket going past recently to get rid of that second recode
to YAML and just save the original PSON catelog to disk as a cache, or am I
remembering wrong?
Oh, I forgot something important.
I ran my test using 'marshall' as format for the catalogs. This is the quickest
for us.
preferred_serialization_format = marshal
So here, the time needed to write the catalog, on disk, using marshaling, is
really slow.
(BTW, I reproduced the problem on 2 different hardwares).
To make sure, comment line 40 of lib/puppet/indirector/yaml.rb on your
client.
If it is now fast then it is the yaml serialization that is at cause.
See ticket #2892 for some explanations.
--
Aurelien Degremont
CEA
--
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.
