Download & Extend
Views » Issues

High CPU usage by PostgreSQL when saving or enabling view

Posted by stodge on June 17, 2009 at 12:20pm
Project:Views
Version:6.x-3.x-dev
Component:Miscellaneous
Category:support request
Priority:normal
Assigned:Unassigned
Status:closed (fixed)
Issue tags:PostgreSQL Code Sprint

Issue Summary

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

Login or register to post comments

Comments

#1

Posted by merlinofchaos on June 17, 2009 at 1:39pm
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.

#2

Posted by System Message on July 1, 2009 at 1:40pm
Status:fixed» closed (fixed)

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

#3

Posted by stodge on July 2, 2009 at 12:17am

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

#4

Posted by merlinofchaos on July 2, 2009 at 12:24am

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.

#5

Posted by stodge on July 2, 2009 at 12:36am

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.

#6

Posted by merlinofchaos on July 6, 2009 at 3:54pm

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.

#7

Posted by Josh Waihi on July 7, 2009 at 5:22am

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

#8

Posted by Shiny on July 10, 2009 at 5:45am

subscribing

#9

Posted by merlinofchaos on July 10, 2009 at 3:34pm

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.