Troy Stribling
2011-Sep-19 22:14 UTC
[Puppet Users] Puppet is very slow when running in AWS
I am using Puppet 2.7.2 with ruby 1.8.7 (2010-01-10 patchlevel 249) and 64 bit Ubuntu 10.4. I have a Vagrant environment which I have been using for development. In the vagrant environment about 5 minutes is required to run all of the modules used for the configuration I have been developing. When I run exactly the same modules in AWS several hours are required. The Vagrant VM has 1 CPU and 1 GB of memory. The AWS VM is an M1.Large with 2 CPUs and 8GB of memory, When running in AWS the puppet process is consuming most a CPU the entire time. Memory usage is low and their is no excessive disk or network IO. The modules are eventually executed without error. Has anyone seen similar behavior? Thanks, -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Romain Pelisse
2011-Sep-19 23:00 UTC
Re: [Puppet Users] Puppet is very slow when running in AWS
I had some issues on my first trial with Puppet on AWS because of DNS resolution. I used Amazon R53 and the all damn thing was very slow (however you could clearly see this issue with wireshark). Maybe this hint will help you... On 20 September 2011 00:14, Troy Stribling <troy.stribling@gmail.com> wrote:> I am using Puppet 2.7.2 with ruby 1.8.7 (2010-01-10 patchlevel 249) > and 64 bit Ubuntu 10.4. > > I have a Vagrant environment which I have been using for development. > In the vagrant environment about 5 minutes is required to run all of > the modules used for the configuration I have been developing. When I > run exactly the same modules in AWS several hours are required. The > Vagrant VM has 1 CPU and 1 GB of memory. The AWS VM is an M1.Large > with 2 CPUs and 8GB of memory, When running in AWS the puppet process > is consuming most a CPU the entire time. Memory usage is low and their > is no excessive disk or network IO. The modules are eventually > executed without error. > > Has anyone seen similar behavior? > > Thanks, > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- Romain PELISSE, *"The trouble with having an open mind, of course, is that people will insist on coming along and trying to put things in it" -- Terry Pratchett* http://belaran.eu/wordpress/belaran -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Troy Stribling
2011-Sep-21 16:52 UTC
[Puppet Users] Re: Puppet is very slow when running in AWS
DNS seems OK. It is looking like problem may be with EBS. I am collecting more data and may write another post later. On Sep 19, 7:00 pm, Romain Pelisse <bela...@gmail.com> wrote:> I had some issues on my first trial with Puppet on AWS because of DNS > resolution. I used Amazon R53 and the all damn thing was very slow (however > you could clearly see this issue with wireshark). Maybe this hint will help > you... > > On 20 September 2011 00:14, Troy Stribling <troy.stribl...@gmail.com> wrote: > > > > > > > > > > > I am using Puppet 2.7.2 with ruby 1.8.7 (2010-01-10 patchlevel 249) > > and 64 bit Ubuntu 10.4. > > > I have a Vagrant environment which I have been using for development. > > In the vagrant environment about 5 minutes is required to run all of > > the modules used for the configuration I have been developing. When I > > run exactly the same modules in AWS several hours are required. The > > Vagrant VM has 1 CPU and 1 GB of memory. The AWS VM is an M1.Large > > with 2 CPUs and 8GB of memory, When running in AWS the puppet process > > is consuming most a CPU the entire time. Memory usage is low and their > > is no excessive disk or network IO. The modules are eventually > > executed without error. > > > Has anyone seen similar behavior? > > > Thanks, > > > -- > > You received this message because you are subscribed to the Google Groups > > "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users+unsubscribe@googlegroups.com. > > For more options, visit this group at > >http://groups.google.com/group/puppet-users?hl=en. > > -- > Romain PELISSE, > *"The trouble with having an open mind, of course, is that people will > insist on coming along and trying to put things in it" -- Terry Pratchett*http://belaran.eu/wordpress/belaran-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.