innodb

Not sure where is the most appropriate post for this, let me know if anybody has suggestion.

I am having performance issues with INNODB. My major issue is that with INNODB I am getting approximately 20 times slower performance than with MyISAM. For the purpose of testing I have used Drupal 7 with devel module installed. Further more I used 2 bare bone servers with default installations so I can do parallel comparisons.

Not sure where is the most appropriate post for this, let me know if anybody has suggestion.

I am having performance issues with INNODB. My major issue is that with INNODB I am getting approximately 20 times slower performance than with MyISAM. For the purpose of testing I have used Drupal 7 with devel module installed. Further more I used 2 bare bone servers with default installations so I can do parallel comparisons.

Hello!

Having a pretty old laptop as my primary development workstation, I'm very concerned about development speed. Under development process I mean the most frequent operations you do when making a website, like:

• installing and configuring modules
• creating and configuring entities (nodes, products) and fields
• theme development

Question:
Has anyone ran Drupal with the Transaction Isolation Level set to READ UNCOMMITTED? REPEATABLE READ is the default setting, but I think for 99% of the sites out there using dirty reads seems like it would be very helpful.

How to set this in my.conf or via SQL command:
transaction-isolation = READ-UNCOMMITTED

We were considering conversion of Tables to Innodb. I have read at many places about the side effects and positive things about Converting to Innodb.

Can we have a list of tables here, which we can convert to Innodb and those which should be kept to MyIsam.

The site is am working on, is having high load and high number of pages are delivered.

On an average, 300 nodes are added everyday. (Not much of Commenting activity)

The pages are served via Boost Module to Anonymous users.

The logged in user activity is also low.

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 :)

Here is my initial post about performance tuning our site http://www.divx.com/ This is mainly a place for me to brain dump and spark discussion and hopefully open up issues to track and get some of these fixes into Drupal core.

Servers

4 - Web servers with 8GB Memory each, Apache 2.2.x + PHP 5.2.x
2 - Memcache Servers with 8 GB Memory each. 9 bins per server
2 - Database Servers with 16GB each running MySQL 5.0.x

Traffic