<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'><br>----- "FGM" <fgm@osinet.fr> wrote:
<br>> From: "FGM" <fgm@osinet.fr><br>> To: "A list for Drupal consultants and Drupal service/hosting providers" <consulting@drupal.org><br>> Sent: Wednesday, March 30, 2011 7:33:09 AM GMT -06:00 US/Canada Central<br>> Subject: Re: [consulting] Server Specs<br>><br>> 3 sec/page, authentified, is high. So is 500ms anonymous.<br>> <br>> You might want to make sure:<br>> - you have correctly enabled your page cache, at least at the "normal" <br>> level.<br>> - you have enabled and set up APC<br>> - you have tuned MySQL beyond its usual default configuration, which is most <br>> of the time set up for a tiny embedded server like a set-top-box.<br>> - you have not been writing queries in your theme, not doing anything heavy <br>> in hook_init(), and not implementing hook_boot() (simplifying).<br>> <br><br>I have run a high traffic site with a good bit of dynamic generation going on. I second all of this.<br><br>Here are the things we did to tune for a massive number of hits. Some or all of the following will help you out, but you can probably get away with picking just a few.<br><br>(1) InnoDB in MySQL is your friend for performance. (To some this may seem counterintuitive, but we found this to work in practice.)<br><br>(2) We have a few tricks up our sleeve with regard to caching. Behaviors that keep the whole cache from being flushed all at once are a definite win, and I'm sure Drupal does this out of the box to an extent. I'd might be able to expound on this later on some of the more exotic approaches or if someone would like to drop me an off-list email.<br><br>(3) Avoid caching in the database. Use memcached or something else.<br><br>(4) If you're running more than one box, watch the latency on your network and quality of your switches. We invested in good quality Cisco gigabit switches with a moderately high packet forwarding rate, and it *did* make a difference.<br><br>(5) Offload images by putting Varnish or Squid in front. They're a lot more efficient at serving images than Apache in my experience, and we saw noticeable differences.<br><br>(6) Add indicies to the database as appropriate.<br><br>(7) If not already off, turn off DNS look-ups in Apache.<br><br>(8) Pay attention to IO. Make sure your database has enough IO horsepower. SSD's are a real win here for the money though reliability is still unproven. It's those occasional events that hit the IO hard that can cause real issues.<br><br>(9) If you're running your site around the clock, turn off pesky processes (some of which run by default as part of most Linux distros) or relegate them to your low traffic hours. We have always had some issues with this kind of thing as there's never a perfect time to saturate the IO.<br><br>> <br>> <br>> ----- Original Message ----- <br>> From: "Fred Jones" <fredthejonester@gmail.com><br>> To: "A list for Drupal consultants and Drupal service/hosting providers" <br>> <consulting@drupal.org><br>> Sent: Wednesday, March 30, 2011 2:17 PM<br>> Subject: [consulting] Server Specs<br>> <br>> <br>> I am looking at site built by a Drupal newbie and I am trying to fix<br>> it up. Truth is aside from the theme, the rest of the site appears<br>> normal. And the theme I am fixing up.<br>> <br>> Now the issue is a new server because the current server is quite<br>> slow. The site gets around 200K pageviews a month, with a high day<br>> getting 30K. I calculate that if we presume around 15 hours of that<br>> day are busy, that's 2K per hour. That comes out to something like a<br>> page every 2 seconds. I am not an expert in busy sites, but I think<br>> this is not too bad actually and that any decent VPS or dedicated<br>> server *should* be able to handle it.<br>> <br>> I turned on devel and I see page execution times of 3 seconds on<br>> average, however. I think that's very high. I will try to analyze if I<br>> can and see what's slowing down this site, but in the meantime here<br>> are my questions:<br>> <br>> 1. People agree that 3 seconds is very high? Yes, yes it depends on<br>> the theme and modules etc. etc. The theme is (now) a fairly standard<br>> Zen sub-theme, nothing special in particular. There are a lot of<br>> modules but it seems that node pages render as fast as views pages.<br>> There are now 30K nodes but I think they want to import a lot more.<br>> The mysqldump file is around 650M. Not huge I think.<br>> <br>> 2. Can anyone give any advice regarding specs for a new server? Or at<br>> least confirm that any reasonable machine with reasonable specs should<br>> be OK?<br>> <br>> Thanks,<br>> Fred<br>> _______________________________________________<br>> consulting mailing list<br>> consulting@drupal.org<br>> http://lists.drupal.org/mailman/listinfo/consulting <br>> <br>> _______________________________________________<br>> consulting mailing list<br>> consulting@drupal.org<br>> http://lists.drupal.org/mailman/listinfo/consulting<br>> <br>> </div></body></html>