displaying admin/build/modules very slow

I've now created a fresh install on my desktop machine and this is still very very slow. I have only enabled a couple of modules (see listing from drush below) and yet going to http://localhost/admin/build/modules/list comes back with

This is the list of installed modules. It's a fresh database - no content.

Has anyone else noticed this? Any ideas what to do? At the moment I make myself a cup of tea whever I want to enable or disable a module...

Which database? I noticed displaying/processing the module list was slow using PostgreSQL on Centos. Assuming I understand you correctly.

MySQL sadly. I wish I could blame PostgreSQL at this point...

Does disabling admin_menu increase the performance?

Since you have devel already installed, couldn't you create a dump of the queries to find out which queries appear unusual often, or at least attach the dump to this issue?

I have been crying about the same issue, and provided the devel log. I beg someone please take a look at this issue.

I saw drupal is generating over a thousand queries when I hit admin/build/modules on a fresh install.
http://drupal.org/node/311626, Please can someone help?

In the spirit of "spread the wealth", I am sharing my solution for my problem, hope it may help you as well.

See #22 in this post http://drupal.org/node/311626

http://drupal.org/node/302638#comment-1101374

From
Page execution time was 22306.34 ms. Executed 3450 queries in 1987.3 milliseconds.

to
Page execution time was 22581.1 ms. Executed 3342 queries in 1938.14 milliseconds.

Reduce number of queries, but the Page execution time is higher?

It's ridiculous, I've fresh Drupal 6.8 installation with no non-core modules enabled and admin/build/modules page is loaded more than 1 minute!

This is a snippet from the report of the devel module:

Queries taking longer than 5 ms and queries executed more than once, are highlighted. Page execution time was 115559.85 ms.

Memory usage:
Memory used at: devel_init()=1.49 MB, devel_shutdown()=12.28 MB.

Does anyone has an idea what's going wrong?

On the same server/database Drupal 5.6 works perfect.

Hello,
I have gone mad in searching why my admin/build/modules not working after installing CCK,views modules on Drupal6.10. I earnestly request to fix out this. I tried the same thing in Drupal 5.6 .Its working fine there.I want the same to work on Drupal 6.10 as I have developed all my modules in Drupal 6.10 :-(

Hi All,

http://www.tmsnetwork.org/blog/content/2008/08/22/drupal-6-slow-administ... worked for me.

According to that it is due to attempting to get update information. So it instructs how to change a single record in the system table.

record is system.filename = 'modules/update/update.module'

Thanks for posting your solution.

- Arie

@tharaka
Thank you for your solution, it worked for me.

I tried the fix above (disabling update module) but that didn't help.

I'm having this same issue as well, very slow loading times.

Take a look at this handbook page and see if any of that helps.

The modules page *is* a slow page -- probably the slowest -- on any Drupal install because of all the server queries Drupal has to make.

Just an update. We bought a new web server but I start realizing the main cause for this is a slow database server or maybe the number of queries? - latest "benchmarks":

Which according to my colleague here is 36 queries per second. What do other people get?

#7:

I have myisam as default and it's very slow even on a brand new install.

sounds like there is a solution coming up soon http://drupal.org/node/512962

Subscribing.

Thanks for taking the time to report this issue.

However, marking as duplicate of #193366: execute various rebuilds when modules are submitted.
You can follow up on that issue to track its status instead. If any information from this issue is missing in the other issue, please make sure you provide it over there.

Disabling the admin menu recovered the problem for me.

I am using drupal 6.14 which includes the patch from #193366: execute various rebuilds when modules are submitted and indeed the performance has improved. But I have done quite a few experiments tracking the time it takes for a load/reload/submit of admin/build/modules page and I have cocluded that when update status is enabled many a times the page load times out after execution time has been exceeded

The question is do we need update status to run on admin/build/modules page or everytime ?

Here is my experiment
------------------------
loading page (F5) 16 sec
enabling update status 97 sec
reloading page (F5) 40 sec
reloading page (F5) 40 sec
disabling update status 53 sec
reloading page (F5) 16 sec
------------------------

take a note that enabling the update status makes the page load 2.5x slower
which in many cases might lead to blank screen when enabling lots of modules
at the same time

NOTE:
- time of completion was reported from firefox pluggin
- I am running on localhost thus no server load other than my page requests

modules installed and enabled in modules directory
admin_menu
cck
filefield
filefield_insert
i18n
languageicons
pathauto
token
views
imagecache
imageapi
imagefield
imagefield crop
wysiwyg
jLightbox
thickbox

i know sun above thinks this is a duplicate but I consider the other issue fixed since it was dealing with rebuilds but feel free to include it in any other issue