Puppet users - Aug 2010 - puppet dashboard takes a long time to display

I''ve been noticing my puppet dashboard is taking longer and longer to 
load up in my we browser the longer I''ve used it. I have roughly 1300 
nodes being managed by puppet. It''s almost as if there is too much data
for it to process. I have about 1 month worth of data in my mysql 
database now. I''ve recently upgraded to version 1.0.3 but it
hasn''t
improved the performance. It''s taking typically around 60 - 90 seconds 
for the page to load...the browser sits waiting for a response from the 
server.

-- 
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.

On 08/04/2010 01:50 PM, Steven L. Seed wrote:
> I''ve been noticing my puppet dashboard is taking longer and longer
to
> load up in my we browser the longer I''ve used it. I have roughly
1300
> nodes being managed by puppet. It''s almost as if there is too much
> data for it to process. I have about 1 month worth of data in my mysql
> database now. I''ve recently upgraded to version 1.0.3 but it
hasn''t
> improved the performance. It''s taking typically around 60 - 90
seconds
> for the page to load...the browser sits waiting for a response from
> the server.
Some things that you can do to make Dashboard run faster:
1. Run it in `production` mode, which is explained further in
application''s README.
2. Remove older reports from the database, e.g. keep only the last 15
days: `rake RAILS_ENV=production reports:prune upto=15 unit=day`
3. Run the Dashboard and its database on the same machine, and give them
enough CPU cycles and RAM to run comfortably.

If these don''t help, it''s likely that you''re running
into performance
problems with how Dashboard is currently implemented. Resolving these
issues is a high priority because it affects sites like yours with many
nodes and reports and is on the schedule for the next major release.

-igal

-- 
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.

I found the root cause of my problem. After running of about 1 month 
using the development environment my log file grew to over 24GB. I had 
no idea this log file was even there since it''s in a less than standard
location (/opt/puppet-dashboard/log/development.log). I switched to 
using the production environment and that initially helped along with 
purging about 3GB of my report data from the database, but ultimately, 
the very large log file was impacting things as well.

Igal Koshevoy wrote:
> On 08/04/2010 01:50 PM, Steven L. Seed wrote:
>   
>> I''ve been noticing my puppet dashboard is taking longer and
longer to
>> load up in my we browser the longer I''ve used it. I have
roughly 1300
>> nodes being managed by puppet. It''s almost as if there is too
much
>> data for it to process. I have about 1 month worth of data in my mysql
>> database now. I''ve recently upgraded to version 1.0.3 but it
hasn''t
>> improved the performance. It''s taking typically around 60 - 90
seconds
>> for the page to load...the browser sits waiting for a response from
>> the server.
>>     
>
> Some things that you can do to make Dashboard run faster:
> 1. Run it in `production` mode, which is explained further in
> application''s README.
> 2. Remove older reports from the database, e.g. keep only the last 15
> days: `rake RAILS_ENV=production reports:prune upto=15 unit=day`
> 3. Run the Dashboard and its database on the same machine, and give them
> enough CPU cycles and RAM to run comfortably.
>
> If these don''t help, it''s likely that you''re
running into performance
> problems with how Dashboard is currently implemented. Resolving these
> issues is a high priority because it affects sites like yours with many
> nodes and reports and is on the schedule for the next major release.
>
> -igal
>   
-- 
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.

Steven,
Thanks for sharing your findings.  I''ve created ticket #4553 to either
add some README documentation about this or somehow setup a default
for log size.
Matt

http://projects.puppetlabs.com/issues/4553

On Mon, Aug 16, 2010 at 3:32 PM, Steven L. Seed <slseed1969@gmail.com>
wrote:
> I found the root cause of my problem. After running of about 1 month using
> the development environment my log file grew to over 24GB. I had no idea
> this log file was even there since it''s in a less than standard
location
> (/opt/puppet-dashboard/log/development.log). I switched to using the
> production environment and that initially helped along with purging about
> 3GB of my report data from the database, but ultimately, the very large log
> file was impacting things as well.
>
> Igal Koshevoy wrote:
>
> On 08/04/2010 01:50 PM, Steven L. Seed wrote:
>
>
> I''ve been noticing my puppet dashboard is taking longer and longer
to
> load up in my we browser the longer I''ve used it. I have roughly
1300
> nodes being managed by puppet. It''s almost as if there is too much
> data for it to process. I have about 1 month worth of data in my mysql
> database now. I''ve recently upgraded to version 1.0.3 but it
hasn''t
> improved the performance. It''s taking typically around 60 - 90
seconds
> for the page to load...the browser sits waiting for a response from
> the server.
>
>
> Some things that you can do to make Dashboard run faster:
> 1. Run it in `production` mode, which is explained further in
> application''s README.
> 2. Remove older reports from the database, e.g. keep only the last 15
> days: `rake RAILS_ENV=production reports:prune upto=15 unit=day`
> 3. Run the Dashboard and its database on the same machine, and give them
> enough CPU cycles and RAM to run comfortably.
>
> If these don''t help, it''s likely that you''re
running into performance
> problems with how Dashboard is currently implemented. Resolving these
> issues is a high priority because it affects sites like yours with many
> nodes and reports and is on the schedule for the next major release.
>
> -igal
>
>
> --
> 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.
>
-- 
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.