Hello,
So we're about to launch our first Drupal website and I am worrying about it's sluggishness even though there's just two users testing the site. We're on Dreamhost private servers (if that's any help) and i already requested for a MySQL virtual private server (its a separate entity, i dont know why) and increase it's RAM. Other than that i haven't done any optimization as i don't have any previous experience with this realm of Drupal. So I would really like to learn about site optimization techniques. This can probably help me too for future Drupal projects that are only on shared hosting with very limited resources.
Thanks a lot and i hope you can point me to the right way of doing things.
Comments
First, you need to figure out
First, you need to figure out what part of the site is slow. Is it SQL query execution? Disk access? PHP execution? OS memory swapping? The network? Merely guessing at the problem and then plunking down more money on arbitrary things to fix it is probably going to break your budget before it fixes your issue.
The Boise Drupal Guy!
Good start
Here's a link that's a good start, and feeds off of what Garrett has said. http://www.morningtime.com/Drupal-6x-Performance-Guide/513
Since the bottleneck could be one of at least 56 things (seriously), this site is a good walk-through of the various layers of technology, and varying levels of expertise/configuration required for each point.
Many of these tips are for "backend" performance gains, basically helping your server spit out html faster (simplified).
A good "frontend" start is to use the site gtmetrix.com, and follow some of the advice they give as it analyzes any page you tell it to within your site according to google's and yahoo's opinions on what makes a site perform well. It's nice because it gives detailed explanations, prioritizes issues, and lets you chart your results over time, all for the low-low price of free.
Good luck
Thanks for your advices, i
Thanks for your advices, i know installed Boost module and it's indeed a lot faster. The only problem is it only does caching for anonymous users and since we're also going to have authenticated users logging in on the site I would also need a caching system for them.
have a look on
have a look on http://drupal.org/project/authcache