Dries has done some benchmarking..
The discussion on the development mailing list boils down to:
We've got to improve non-cached performance if Drupal wants to remain competative.
(because its easier for other products to improve their caching and catch up on the front).
So where do we start? What does the code profile look like? Where are the bottlenecks?

Attached are a couple of profiles from my laptop serving the default front page (/node) from localhost.

The first is a stock 4.7 install. The second is an up to date (Aug, 17th 2006) CVS checkout.

Certainly more profiling needs to be done (not all pages are created equal in Drupal), but this is a starting point.

Draw your own conclusions from the results.

andre

CommentFileSizeAuthor
#4 profile_0.png156.21 KBdries
#2 profile.png66.32 KBandremolnar
#1 ProfileCVS-non-cached.png41.12 KBandremolnar
profileCVS.png42.79 KBandremolnar

Comments

andremolnar’s picture

andremolnar commented
StatusFileSize
new ProfileCVS-non-cached.png41.12 KB

Non-cached code trace.

andremolnar’s picture

andremolnar commented
StatusFileSize
new profile.png66.32 KB

For comparison - Drupal 4.7 (cached)

Joe Wiz’s picture

Joe Wiz commented

subscribing

dries’s picture

dries commented
StatusFileSize
new profile_0.png156.21 KB

Here is another graph.

killes@www.drop.org’s picture

killes@www.drop.org commented

I like fancy pictures, but I'd like to see them interpreted in a way that allows me to conclude where we should look for improvements. Some url to an explanationm on how to read the graphs would help for starters.

LAsan’s picture

LAsan commented
Version: x.y.z » 7.x-dev

Any progress on this task?

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Active » Closed (duplicate)

I'm pretty sure this issue is too old to be relevant anymore and there are other issues to track performance for Drupal 7.

(Sorry for pinging the participants, I'm trying to clean up a few old
issues)