Deprecated - Performance and scalability

can any buddy suggest me how to create sitemap for my drupal site

My company has just done a migration to Drupal. Everything works fine. However, when multiple users use the search engine, MySQL database crashes causing the site down. It is a bit unstable. I'm seeking anyone here who can give some advices regarding the server setting or configuration. Below are some of the current spec:

Drupal 4.7.7 (30000+ nodes)
PHP 5.1.2
MySQL 5.0.24
IIS 6.0

Drupal is running in a dedicated server which is Intel Xeon 3.0GHz with 4GB of RAM.

After downloading and installing the Revision Moderator and running the patch for 5.1 version, the module doesn't seem to function.

I've been playing around a bit with how I want to setup my Drupal development vs. production installations. I'm a beginning subversion user, and this is my first major attempt at using subversion (or anything, for that matter) for version control of a project.

I'll need two environments, one 'development' environment, and one 'production' environment.

They would idealy be running off of two separate installations of drupal.

Here's how I've set it up thus far:

I've created a repository, and a new project titled 'drupal', where I house my drupal installation (and any revisions, of course). This would include all directories within the default drupal installation, as well as any custom modules or themes.

I've checked out two copies of the project from the repository as:

/drupal-dev
/drupal-prod

They are identical, as they are both copies of a version of the repository project (say, version 1).

This works as expected. My concern comes from files that have been uploaded into the production version (in the /drupal/files directory), as well as any files generated by drupal (a custom logo generated by the color module, for example).

I am currently running about 10 sites or so on a multisite setup.

Right now I have about 5,000 or so files in my files directory. I am wondering if it is good to continue having every file go to my files directory, or if I should start spreading it out a little now. Perhaps every 1,000 files I create a new subdirectory that will hold this content? Is there already some existing module that breaks the files directory down so that it doesn't put all the files in one directory?

Any help on this topic would be super helpful.

Thanks,
Quinton

Managing the whole chain: Dev - Integration - Staging - Production is a major issue for Drupal. It's one of the Drupalcon2007 conclusion. As we discussed during the Building High Traffic and Scalable Businesses with Drupal , it is imperative for us to have migration methods and tools.

At France24, we are massively switching on Drupal. At the end of the year, france24.com website and several satelites will be using Drupal 5.2. We need a simple architecture to allow our team of 5 developers :

- to work on the same code repository and database.

- test the function on an integration environment

- publish content and edit configuration on a staging environment

- easily migrate on production or "synchronise" with a production environment.

Today, a majority of the Drupal dev i asked this question aswer me : "we are working directly on the production server, reporting manually the configurations we've made on a staging environment..."

At France24 we worked during 2 months to find a simple solution to answer this question. We have mounted a complete dev -> integration -> production environment responding to our needs. For some days, this platform is used by our team. It seems to work correctly, but we are still testing it. If you want to join the experiment and share, you are welcome.
Synthesis

So here's is our solution.