I just starting noticing that views take a long time to enable or save; 'top' is showing that postmaster (PostgreSQL's process) is taking 90% CPU. Is this normal?

Thanks

Comments

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Fixed

This is probably normal; saving or enabling a view requires a menu rebuild in case paths changed. It's about the same as you'd see visiting the modules page.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

stodge’s picture

stodge commented

I'm not convinced - see http://drupal.org/node/506208.

merlinofchaos’s picture

merlinofchaos commented

It's about the same as you'd see visiting the modules page.

And the modules page is slow for you under pgsql. What aren't you convinced about? Views clearly has nothing to do with this.

stodge’s picture

stodge commented

The module list requires a menu rebuild, which my testing has shown is significantly slower under PostgreSQL that mySQL. Therefore I say again, I'm not convinced.

merlinofchaos’s picture

merlinofchaos commented

menu rebuild is NOT a Views function. There's nothing I can do about it. So you can be not convinced all you like, and I still can't do anything about it.

josh waihi’s picture

josh waihi commented
Issue tags: +PostgreSQL Code Sprint

I've recently noticed this, menu_rebuild is quite draining. Promoting to PostgreSQL Code Sprint. More info, if you want to be apart of it http://geek.joshwaihi.com/content/drupal-code-sprints-postgresql

Shiny’s picture

Shiny commented

subscribing

merlinofchaos’s picture

merlinofchaos commented

Could I get you to open a new issue in the Drupal queue for this? The Views queue isn't the place for it, and just moving this to the Drupal queue will have a whole bunch of irrelevant stuff that will probably have a lot of peopel stop reading it before it becomes important.