Jacob: Thanks. I fixed the whitespace and changed `logwatch` to `logrotate`. Merged into `next`.
-igal On Wed, Sep 29, 2010 at 11:40 AM, Jacob Helwig <[email protected]> wrote: > Comments inline. > > On Wed, 29 Sep 2010 10:42:37 -0700, Igal Koshevoy wrote: >> Date: Wed, 29 Sep 2010 10:42:37 -0700 >> From: Igal Koshevoy <[email protected]> >> To: [email protected] >> Subject: [Puppet-dev] [PATCH/puppet-dashboard 1/1] (#4876) Document tips >> for >> improving performance. >> X-Mailer: git-send-email 1.7.2.3 >> Message-Id: <[email protected]> >> >> Users keep asking how to improve the performance of their application, and >> the documentation is a great place to provide these common tips. >> >> There are plans to improve performance in the future by making major >> changes, but these tips will still be useful for those running larger sites. >> >> Signed-off-by: Igal Koshevoy <[email protected]> >> --- >> >> Published to repository at >> http://github.com/igal/puppet-dashboard/commits/feature/next/4876-document_performance_tips >> >> README.markdown | 14 ++++++++++++++ >> 1 files changed, 14 insertions(+), 0 deletions(-) >> >> diff --git a/README.markdown b/README.markdown >> index 025c331..485faac 100644 >> --- a/README.markdown >> +++ b/README.markdown >> @@ -306,6 +306,20 @@ Third-party tools that can help secure a Puppet >> Dashboard include: >> >> http://username:passw...@hostname >> >> +Performance >> +----------- >> + >> +The Puppet Dashboard slows down as it manages more data. Here are ways to >> make it run faster, from easiest to hardest: >> + >> +* Clear the Ruby on Rails logs. You can zero all these logs by running >> `rake log:clear`, or use a tool like `logwatch` to archive old files in the >> `logs` directory. > > I think you actually meant logrotate here? logwatch is just for > analysis, and reporting, as far as I'm aware. > >> +* Optimize your database by running `rake RAILS_ENV=production >> db:raw:optimize` from your Puppet Dashboard directory, this will reorganize >> and reanalyze your database for faster queries. >> +* Run the application in `production` mode, e.g. by running >> `./script/server -e production`. The default `development` mode is >> significantly slower because it doesn't cache and logs more details. >> +* Run the application using multiple processes to handle more concurrent >> requests. You can use Phusion Passenger, or clusters of Thin or Unicorn >> servers to serve multiple concurrent requests. >> +* Prune your old reports, see the "Database cleanup" section in this >> document. > > You've got some trailing whitespace on this line. > >> +* Run on a machine with a fast, local database. >> +* Run on a machine with enough processing power and memory. >> +* Run on a machine with fast backplane, controllers and disks. >> + >> Debugging >> --------- >> >> -- >> 1.7.2.3 >> > > Other than those two comments: Looks reasonable. > > -- > Jacob Helwig > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iQGcBAEBAgAGBQJMo4g3AAoJEHJabXWGiqEBNiEL/A6/emhZifbhzUscqwZMizcF > 88AaQFGnqA5JgmRKgbHTi8nHwntTe8gCJltFfN0XmHjYJSmRZwFpo2qTUjOEsJFh > SEO6TzzCooSZYd+yvdODLPnHtyiQPNg2MtF0QbnHBkpJf5pN1EjdjFazYHYqwUc2 > X7luhXDTb+M+Iv6zhH6jl8fYBmWSUWpwcjUY8CbKvjjIN4JovzSCIVyvXVR1/pQl > HQUIzsa125oXjg3P4jymBgmuBnMnDlU+gxm/MoEMBJ/mXO9lCJ0wgVZJhUE9ajTO > dFUS7magPP4GMw/lXySXWmhX7fmXbU53or3oWTebxKx47Z4VPctFaspMBmR8Uzlq > XHi2FaIXC7pmbQCkO5881OOb5xbQ9+POL1ihqPte7cGlMrY4NshfLZQnaOrmNvwd > /g4DZFPxUGF0FwraOiRp7MDThhpk2zIj2tDk2dPvBlYbGClvdPuLc31f3Fdd1k/d > h7NmeHtDQBM31UwrMYQ7Noi8F1a+XB8+2zyZLI5/GA== > =QKFX > -----END PGP SIGNATURE----- > > -- 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.
