Search

So, one of the big things with static file serving is that it requires an entire Drupal bootstrap, which sucks up a lot of system resources. We have work to do in Drupal/the File API to support some interesting scalability options, remote files, etc. etc.

But, I think there are some interesting models for doing highly scalable static file serving outside of Drupal (and Amazon's S3 is cool).

• Fast and Secure Web Apps by Rasmus Lerdorf
• Hight Traffic Web Development from /dev/random
• PHP Benchmarks
• Digg PHP's Scalability and Performance

File caching for Drupal 4.6 http://drupal.org/node/61227
File caching for Drupal 4.7 http://drupal.org/node/45414

Please test and review for inclusion in Drupal 4.8.

http://osinet.typhon.org/riff.org/blog/2006_05_14_data_model_for_drupal_...

His comment on node_access_realm was very interesting. Anyone want to try it and do some profiling? OG module would be a good use case to profile.

I just posted an experience installing og on a multilingual site. The short version is that it ground to a halt because of the t() function. Maybe og is still a little early in it's 4.7 release, but I think it's an example of bad things happenning to good modules. Does anyone else have any experience, ideas about scaling t()? I can see there's some caching going on, and maybe I just need to adjust a cache size somewhere ...

[a while later]

aha, here it is: http://drupal.org/node/42463 - it's a problem with 'incomplete translations', and a proposed sql index fix didn't make it into 4.7 as per the discussion.

Just make sure, you have magic_quotes_gpc variable in php.ini set to Off, otherwise, Drupal will walk all $_GET, $_POST, etc. arrays to manually fix magic quotes. This can affect Drupal performance.

This is about PHP common development mainly, some advices to improve strings parsing performance.

I just noticed 35 occurences of ereg* functions in Drupal code (most of them in modules, 4.6.6).
This short story is just a memo to advise all developers NOT to use ereg* functions and use preg_match instead, which is significantly faster. I would also like to do same stats in Drupal 4.7 and collect some volunteers to provide patches replacing ereg with preg_match.

Any volunteers?

<

blockquote>
Hi, I recently switched from phpbb to drupal. (http://drupal.org/node/44368)

Here is my configuration

• web server: Dual Xeon 3.0Ghz (32bit), 2G RAM, SATA HDD
• db server: same as web server (physically different server)
• software: apache 1.3.34, php 5.1.2, mysql 5.0.18
• total number of nodes: 70,000+
• total number of comments: 330,000+
• total number of users: 25,000+
• Usually there are 150+ anonymous users and 50+ registered users (by checking Who's online block)
• Modules: most core modules (4.7) except archive, book, drupal, legacy, ping with contributed modules (adsense, codefilter, favorite_nodes, google_analytics, logintobaggan, nmoderation, subscription, taxomony_access, urlfilter, votingapi, comment_upload, tagadelic)

Static File Caching http://drupal.org/node/45414#comment-105354

Fastpath: http://drupal.org/node/45414#comment-105355

We are looking for reviewers to review the code and test it.