optimization

Hello Everyone,

I have a website with 100k Visitors/Day , I am a newbie in Php and Servers, when a downtime occurs managed hosting guy was resetting the server and I was optimizing the databases and I was optimizing the DB everyday and I was fine.

But this week site became to crash twice a day. And Reboot/optimize only works for 5-6 hrs and it crashes again. My hosting guy said it is caused by cache_page table in mySQL and it gives ~300MiB overhead in 2hrs after mysql optimization. And he said its a wrong method to keep cache in database it causes this errors.

Authcache offers page caching for logged-in authenticated users. This allows Drupal to load pages in 1-2 milliseconds and take the load off the the database & processor. Please help test this module (the site I was creating this for got axed, but I continued development on this module). Feedback & patches are welcome. This module can be used for anonymous users (it's faster than Drupal core since the database won't be hit), supports the statistics module, and can cache blocks of user-customized content.

Many thanks to Steve Rude for his work on the Cache Router module, which Authcache uses as its caching system.

This is how it works:

So supposing you have several sites on D5 that won't get upgraded to D6 (to take advantage of the syslog support) for several months yet due to workload, what are good ways to optimize InnoDB so that Watchdog can write faster, i.e more concurrent INSERT statements, rather than taking down the site if things get fubar'd? Thanks :)

I just wrote a new article called How I Survived a 2300% Traffic Increase With Drupal. It documents my experience with hitting the front page of Reddit, and some of the steps I took to make sure my site stayed online.

I also included some nice traffic graphs and statistics. If you ever wondered what kind of numbers to expect from a front-page link on a big social news site, be sure to check it out.

--
John Forsythe

I'm assuming it's too late, but if not here's an easy performance win for D6:

http://drupal.org/node/215080

<

blockquote>The type column of the {system} table is currently a varchar(255) field. Yet in 99% of all Drupal installations it stores either the text 'module' or the text 'theme' and nothing else. This is already a strong case for making it an int column and defining constants for module and theme. Then, on every page, there is this query:
SELECT filename FROM system WHERE name = 'user' AND type = 'module';

Introduction

projectstars is a new business network which gives experts the chance to show off their experience, network, and find work. Consisting of 300 enterprise communities, we are the first business network to be giving stock to our members in a 'Blog for Stock' event where every three months the top 100 projectstars receive shares in projectstars inc..

Our requirements

OpenCraft hosted a 3.5 hour seminar that I presented on Drupal performance tuning and optimization. You can find the slides from the presentation there, which can be useful to some of you.

In case you have not seen it, there are a bunch of articles on Drupal performance tuning and optimization at 2bits.com.

According to my devel module logs and lots of watching the query lists, the query that costs us the most in all of Drupal core is this one:

SELECT DISTINCT b.* FROM blocks b LEFT JOIN blocks_roles r ON b.module = r.module AND b.delta = r.delta WHERE b.theme = S AND b.status = D

Let the brainstorming begin; what can we do to improve it? Are there enough indexes? Can we avoid the DISTINCT? Are there other options?