performance

I'm curious what people think about the pros and cons of turning on Database Logging in Drupal. In particular I want to know if you see a noticeable performance hit. My site could benefit from knowing who is hitting what, but I'm concerned about performance. Anyone have some experience with Database Logging on a production site.

I posted an feature request for Drupal 7, but on second thoughts I think it fits here better: #363891. I think Drupal could gain performance using automatic code generation.

We have a website and we want to migrate to drupal. I have never build a website with drupal before. we might have 200,000-300,000 new pages in {nodes}.body each month. for the current website we had to denormalize database and call a second query to select the longText field and we had a significant performance gain. Can we somehow denormalize the nodes table and separate the body field. what do u think ?
you can also check this address to see an example of vertical partitioning performance gain.

Hi all,

I initially posted here in the forums, but catch suggested I should post here: http://drupal.org/node/362511

Duplicate content, but here's the post again:

Just throwing this out there. I have been using the Cache Router module to implement Memcache in Drupal 6.x. It says it "refactored" the Memcache API module to include Memcache support, which seems a bit odd. But it works.

Hi guys,

Has anyone noticed a performance impact when the Drupal 5.x database is split for a multisite setup?

CCK: 6.x-2.1
Drupal: 6.8

I am working on a module that needs to fetch sets of nodes based on various criteria (I don't think the criteria isn overly important for this discussion). The content nodes may span all content types installed on the site. I need to fetch a list of all the nodes matching my requirements and all of their fields/content.

I need this basic functionality:

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

Query 1:

field1:value1 field2:value2

Query 1 reversed:

field2:value2 field1:value1

.

Does it make a difference? Would it be better for performance to use the field first which yields the smallest sub result set? Or does Solr/Lucene handle this all by itself?

Hello,
I am planning on doing some benchmarking to assess two models of CCK used in Drupal 5.

I support a D5 site that has been averaging around 18 secs load time for the front page (it has lots of external httpd calls, javascript, css files, etc). The architecture consists of a redundant front-end load balancer along with a pair of Squid caching servers, a RHEL5 GFS 4-node cluster, Memcached cluster (1GB per server, 4 servers total). D5 site is running the Memcache API as well.

LoadRunner Setup: 20 Minute Run-Time, 100 Virtual Users (Starts at 2, increases by 2 each 10 seconds)