Switch CMSes, you'll be better off. I have the pain of running Drupal, too.
Your DB host is probably good enough, unless you're doing insane amounts of page views. What you need is Drupal optimisations. Here's just a few: - drupal keeps both it's sessions and cache in the DB. Change to memcache - the views module is horrible. Get rid of it and write your own queries - for pete's sake don't turn on the watchdog module, especially on debug. That, too goes in your db - avoid taxonomy - it does evil hiearchical queries et cetera ad nauseam :-) On Wed, Apr 21, 2010 at 4:31 PM, shamu...@gmail.com <shamu...@gmail.com>wrote: > I have a 1.5G database which feeds a CMS web application (Drupal). > > Right now I am hosting it with a 1.5G RAM VPS and I feel it is too slow. IO > and CPU are high. So I am planning to upgrade it to a dedicated serer. > > Here are two choice of my server: > > 1. Intel Pentium G6950 (Dual Core), 2xSATA Drive (no RAID), 8G RAM > 2. Intel Xeon X3210 (Quad Core), 2XSATA drive (no RAID), 4G RAM. > > I know the best way to do this is to benchmark the two servers, but I can't > do that, can only pick one. Could anyone of you tell me which one is better > for higher MySQL performance, based on your experience? > > Thanks. > -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
