'Carefully' re-reading ur original post now I know I am way off base. Apologies.
Tony Sent on the Sprint® Now Network from my BlackBerry®
-----Original Message----- From: Anthony Malkoun malkouna@yahoo.com.au Sender: support-bounces@drupal.org Date: Tue, 26 Jul 2011 11:06:58 To: support@drupal.org Reply-To: support@drupal.org Subject: Re: [support] Optimizing Drupal6 + finding bottlenecks
Just some semi random thoughts...
If trying to find a sporadic bottleneck and using MySQL I find the slow query log to be invaluable. For general slowness a quick problem determination can be performed by installing the devel module and turning on performance tracking. Long term performance monitoring probably needs something like Cacti installed. If most of your traffic is to anonymous users think about using Drupal's inbuilt cache. I've had some success with non anonymous use by setting up mod_deflate to compress everything.
On 6:59 AM, Marilyn Langfeld wrote:
I just attended CapitalCamp in DC, and one of the sessions was High Performance Drupal: Step by Step. http://www.capitalcamp.org/sessions/high-performance-drupal-step-step
The slides from the session are available on the page referenced above. The presenter, Fabian Franz from Trellon, made one point early on:
/"If you build the house on one pillar, it'll not //hold long ..."/Then went on to say the four pillars of high performance for Drupal sites are:
* Pressflow / Drupal 7 * APC * MemCache * Varnish and BoostIt may not possible to use Pressflow (with an installation profile). In that case he suggested to use the other three.
The slides have a little more detail though the presentation included much more, and he showed how quickly all four could be added using command line His style is a somewhat unusual (you'll see if you check out the pdf), and the information seemed good. See what you think.
On Mon, Jul 25, 2011 at 10:08 AM, Liviu Nicolicioiu <liviu.nicolicioiu@epoint.ro mailto:liviu.nicolicioiu@epoint.ro> wrote:
Check your cron usage, the execution time.