I have drupal up and running (on both web servers on windows XP) but it is extremely (5-90 secs / each request especially admin-->modules). I researched this topic and tried many methods and all did not remedy the problem. Here is some things I did:

1. Disabled the update module
2. Increased memory_limit to over 512M
3. Increased the timeout time to over 180s
4. Removed excess CSS / JS.

I really enjoy using drupal but it is frustrating when it is really slow on the localhost. Does anyone have another solution or a fix to this problem? It is all over the web and there isnt a clear solution...

Comments

sai571’s picture

Yes i agree with you that "admin/build/modules" can be slow. But there is indeed a considerable amount of processing that takes place when you visit that page.

Drupal system has to find out all the modules that are present in various directories (i.e., a filesystem operation). That's y it takes so much time, the time may vary depending on your system configuration also, so can't help it if your system is slow let alone the webserver.

lostron’s picture

It is OK if the module page is slow since that page does not get used that often. My main concern is all the other pages. I tried this setup on two computers both of which are fast Duo Core 2 machines.

ludo1960’s picture

Editing your php.ini and make realpath_cache_size=2M and uncomment skip innob in your my.cnf mysql file, restart apache and mysql

rgoodine’s picture

This worked for me (on Vista, XAMPP)! Thanks!!

What does it mean that I've changed this variable?

BasZer’s picture

what do you mean with, and how to do this:

uncomment skip innob in your my.cnf mysql file, restart apache and mysql

s.daniel’s picture

Check for \mysql\bin\my.ini line 131 however MySQL is not starting with this setting uncommented here. (Win current XAMPP release)

The other options do seem to have a positive effect though.

Anonymous’s picture

This works for me.
Thanks so much for sharing.

bigupbaby’s picture

Hello, thank you ludo1960, i'm working on drupal 8 and windows 10 and realpath_cache_size=2M solve my very slow xampp! thank you so much

lostron’s picture

I reformatted another computer and installed xampp and drupal on it and drupal runs really fast. I am certain that I have a program that is causing problems with my drupal installation...

Anonymous’s picture

Any other solutions? I dont feel like reformatting my system. :\

bryanb229’s picture

good stuff.

beyond67’s picture

What helped me also was renaming my my-large.ini to my.ini in the mysql directory. The my-large.ini is configured for systems with more ram.

charlie-s’s picture

Changing to the large or huge mysql .ini file doesn't make a difference for me. Neither does increasing PHP execution time, memory, etc., to rediculous amounts. I stumbled into a post about how just dropping WAMP or XAMP alotegether is the way to go and to use UniServer --- no luck. Still got these slow page loads (like the home page or a blog entry, admin pages take 60+ seconds). All of this makes me think it's something simple with a firewall or network settings. I'll post back when I've found a proper solution.

charlie-s’s picture

Dunno. Disabling AVG, Windows firewall gave no change. Uniserver gave no change. I up'd the memory settings, time limits, etc and restarted WAMP 2 several times with no change.

After a system wide reboot, however, I am noticing very quick speeds again :)

Perhaps make sure you're using Myisam vs innodb tables, up the mysql memory stats, up the php memory stats, and restart you're entire system.

muratsalma’s picture

Stomper’s picture

I was suffering major slowdowns using Drupal (6x) on XAMPP in XP. It got so bad that I would get XAMPP errors since there was no response in 60 seconds etc when just navigating around the site.

I cleared the cache (under "Performance") and it seemed to have helped quite a lot. I think that was first time I had ever cleared the cache in months(?).

Hope this helps

rockallite’s picture

It's about MySql tuning. See here:
http://drupal.org/node/348202#comment-4295574

charlie-s’s picture

If your end server is going to be Linux, then I recommend VirtualBox with a Linux VM as your test environment. You'll have access to all the settings you need.

ludo1960’s picture

steveburge’s picture

We struggled with this for a long time during our training classes.

Localhosts with Drupal 7 would start off reasonably quickly. But as extra modules were added the servers would slow and slow. By the end of a day's training, /admin/build/modules/ would often take 10 minutes or more to load.

I think that problem has lessened as more D7 contrib modules have become stable, but the only really reliable solution we found was Acquia Dev Desktop http://www.acquia.com/downloads

s.daniel’s picture

Here is a drupal optimized ready to use ubuntu development machine for virtualbox:
https://drupal.org/project/quickstart

Asogan’s picture

I'm no expert but I initially tried XAMPP with Drupal 7 - painfully slow.

I then used the Acquia Development install, which is an 'all in one' install (includes AMP). It's hitting lightspeed compared to my previous experience. Install was much, much easier too.

muranod’s picture

Wow. I've been just dealing with the slowness, and then found this thread. Thanks for the suggestion - realpath_cache_size=2M in php.ini (applied through the Wamp64 interface) made a huge difference. No more wasted time waiting for page loads!