Deprecated - Performance and scalability

I want to publish the photos, audio, video uploaded by users to a CDN provider's servers (akamai) to reduce the traffic from the drupal servers from serving rich content. Has anyone done this and what it would take to change the modules to do this?

Is it simply changing the storage location from file system to a URL?

Thanks - a newbie who loves drupal

David

This page has been getting slower and slower for quite a while, can anyone shed some some light on how I might be able to speed it up ?

It takes minutes to load and is driving us all nuts.

There's around 35000 nodes all with alias's, 40 000 odd terms if that makes a difference. Most of the content (99.999%) is a very simple CCK type that originated in 4.7, but the site was upgraded to 5.1 recently, though the slowness pre-dates the upgrade.

Iam using latest drupal 5.1

I installed the memcahed libraries, pecl-memcache extension for php(my phpinfo shows it). memcached service is running.

I added $conf = array(
// The path to wherever memcache.inc is. The easiest is to simply point it
// to the copy in your module's directory.
'cache_inc' => './sites/all/modules/memcache/memcache.inc',
); to the settings.php

I applied the patch file that came with memcache module

I Truncated cache, cache_menu tables as told in the Readme files.

But I see blank pages.

Hi all

If somebody can give me some help with this:


# Time: 070715 20:28:05
# User@Host: portal2[portal2] @ localhost []
# Query_time: 4 Lock_time: 0 Rows_sent: 5 Rows_examined: 306451
SELECT node.nid, node.type AS node_type, node.title AS node_title, node.changed AS node_changed, users.name AS users_name, users.uid AS users_uid, node.created AS node_created, node_counter.daycount AS node_counter_daycount FROM node node LEFT JOIN users users ON node.uid = users.uid LEFT JOIN node_counter node_counter ON node.nid = node_counter.nid WHERE (node.status = '1') ORDER BY node_counter.daycount DESC LIMIT 0, 5;
# Time: 070715 20:28:06
# User@Host: portal2[portal2] @ localhost []
# Query_time: 3 Lock_time: 0 Rows_sent: 5 Rows_examined: 306451
SELECT node.nid, node.type AS node_type, node.title AS node_title, node.changed AS node_changed, users.name AS users_name, users.uid AS users_uid, node.created AS node_created, node_counter.daycount AS node_counter_daycount FROM node node LEFT JOIN users users ON node.uid = users.uid LEFT JOIN node_counter node_counter ON node.nid = node_counter.nid WHERE (node.status = '1') ORDER BY node_counter.daycount DESC LIMIT 0, 5;
# Time: 070715 20:28:07
# User@Host: portal2[portal2] @ localhost []
# Query_time: 4 Lock_time: 0 Rows_sent: 5 Rows_examined: 306451

Egads, all I want to do is get the program to stop stacking my primary menu items on top of one another, but space them out across the top of the page. The words are English, but they do not assemble themselves into coherent English sentences in the Adminstrator mode. Can anyone point me to what I'm sure, if I spoke Drupal, will turn out to be a simple solution?

Also, I have no clue how to make the program re-order sub-menus (lists? am I using the right vocabulary?)

Thanks, ben

Am I correct in thinking that judicious use of subdomains may improve performance and scalability? My thought is that if my site can be divided into two (or more) separate "portions" I am better off with those separate areas being housed within their own subdomain.

The trick, of course, is to define "portion". I'm thinking of a subset of modules that work together but are not needed (at all) by the remaining (or a different) subset of modules. The classic example of this would be a forum. We frequently see that a site at www.example.com will have its forum at forum.example.com. In this way, the portion of the site devoted to forum processing deals with fewer modules than it otherwise would. And the rest of the site similarly deals with fewer modules than it otherwise would.

I guess what I'm getting at is that many of Drupal's callback functions can be made more efficient due to the fact that each subdomain would have fewer modules to process.

Am I offbase?

If I'm not offbase, doesn't this mean that a properly optimized Drupal installation will have a number of subdomains, the purpose of which is to improve performance and scalability in this manner?