By j_p on

Hi.

I'm just trying out Drupal, and I'm running it on WAMP and XP Pro, on a plenty powerful machine. Accessing administer > modules is painfully slow, and enabling/disabling modules can take 35 seconds. I only have two extra modules installed (poormanscron & CCK) - and the problem occurs whether they are enabled or not. A search of the forums shows that this an quite a common issue (I've spent a few hours trying all the suggested solutions), yet there is no definitive solution (apart from maybe Vista where you can # out localhost in \etc\hosts). It appears to only be an issue in Drupal 6.

Obviously this isn't ideal, and it's putting me off from using Drupal a bit - I'm sure there must be others in the same boat.

Cheers.

⋅ Categories: Drupal 6.x

Comments

duozersk’s picture

duozersk
he/him
Primary language Russian
Location Moscow
commented

You can try the Site Configuration -> Performance: Page Cache setting set to "Normal"... it should speed up loading of the Modules page.

AndyB

j_p’s picture

j_p commented

Thanks for the suggestion duozersk - unfortunately it has no effect.

shaunak’s picture

shaunak commented

Set the "relpath_cache_size" to 2M. By default its set to ridiculously low levels.

Also make sure that you are using MyISAM tables.

vonn.new’s picture

vonn.new commented

Can you please help a newbie find this parameter? This sounds like the same problem that I am having.

danny_joris’s picture

danny_joris commented

I think you mean "realpath" instead of "relpath".

It's located in php.ini .

wamp icon > PHP > php.ini

shaunak’s picture

shaunak commented

I am so sorry, I did mean "realpath_cache_size".

Its on line 283 in the php.ini.

danny_joris’s picture

danny_joris commented

This gives me no better results actually. I'm starting to go crazy on how slow Drupal on wamp really is. I read so many different sollutions everywhere, but none will actually work.

Any other suggestions?

tommeir’s picture

tommeir commented

I have the same problem. Loading the module page is a real pain in the Ass with wamp.
Anybody have an idea why this is happening?

the1who’s picture

the1who commented

This step has helped me on a WinXp Home machine. I changed from the 16K commented line by uncommenting and changing to 2M. It went from a 54 second page load each time to a 17 second page load. I think for a local system there might be a way to improve the speed, so still searching for improvements, will take the advice about checking the MySQL. For now though, I thought I'd help those that use WAMP 2 and at least report this was an improvement for me in way of 37 seconds. The last load I did before submitting this was down to 11 seconds.

Matthew

asd123asd5’s picture

asd123asd5 commented

hey guys, are you all using wamp 2? becuase I was using 1.7 before i upgraded to 2 with my upgrade to vista and 1.7 was working quite quick. Now with wamp 2 it's slow as hell. The most major change between wamp 1.7 and 2 from what i can see is the upgrade to apache 2.

anybody have any ideas?

asd123asd5’s picture

asd123asd5 commented

to put it into perspective:
My modules page loads at 1.816s on wamp 1.7 (xp).
My module page loads at 139.58s on wamp 2 (vista).

Note: The installations are exactly the same.

unbelievable.

adam_b’s picture

adam_b commented

This rings a bell... I was working on a non-Drupal project a while back when Vista first came out, and we had very nasty speed issues. The problem turned out to be some default security setting in Vista - unfortunately I can't remember the details, but disabling it fixed the problem.

I've used Uniform Server installations in XP on a moderately-powered laptop several times with no problems.

juicytoo’s picture

juicytoo commented

Hi,

try turning off firewall.

cheers
Ed

kswan’s picture

kswan commented

I was able to resolve this problem by changing the MySQL storage engine from Innodb to MyISAM. You can see my blog post related to this at http://kswantech.com/blog/slow-menu-rebuild-drupal.

BTW, when you visit administer -> modules a full menu rebuild is run. In my case, that was the slow process.

heine’s picture

heine commented

Last time I checked the problem was not InnoDB vs. MyISAM. While InnoDB is enabled and used, it is by default not suitably configured. If you do configure Innodb correctly, you can keep using InnoDB without any trouble. So, set buffer pools, a data_file path and file_log sizes.

See the "other" my.ini files for examples.

asd123asd5’s picture

asd123asd5 commented

I wouldn't suggest changing this anyway, unless you intend to run your mysql storage engine as MyISAM on your live server also...