Performance tuning tips suggest disabling the core "update" module on "production" sites however to do this will require removing dependancy on it.

http://colans.net/blog/drupal-7-performance-optimization-options-and-che...

Tried to disable the core "update" module but found it has a lot of dependancies:

drush dis update
The following extensions will be disabled: update, wetkit_update, wetkit_core, wetkit_wetboew, wetkit_migrate_content_types, wetkit_pages, wetkit_migrate, wetkit_menu, wetkit_widgets, wetkit_layouts, wetkit_bean, wetkit_metatag

Comments

joseph.olstad’s picture

joseph.olstad
Primary language French
commented

To allow us to turn off the update module could we add this line to the the wetket modules .info file(s) ?
features_exclude[dependencies][update] = update

?
any thoughts?

Our prod site doesn't have internet access so it cannot possibly use the update module, so it's basically causing performance issues because when cron is fired there is waits for the timeout on update that never reaches anywhere because internal requests to external wan is blocked.

sylus’s picture

sylus commented
Status: Active » Reviewed & tested by the community

I am fine with doing this as it allows for us to turn it off but won't affect the update manager for other people using WxT so sounds good!

joseph.olstad’s picture

joseph.olstad
Primary language French
commented
Status: Reviewed & tested by the community » Needs review

Option 1 add features_exclude to wetkit_core

  • features_exclude[dependencies][wetkit_update] = wetkit_update
  • add enable wetkit_update to the installation profile (wherever/however that is done)

Option 2 add features_exclude to wetkit_update

  • features_exclude[dependencies][update] = update
  • this option doesn't really make much sense as wetkit_update won't work without update module so why enable it without the "update" module

Soliciting feedback: Option 1 seems logical to me, however if we do option 1 would we have to add an "enable wetkit_update" to the install profile as currently it's automatically enabled when wetkit_core is enabled.

If we do Option 1, this should remove the dependancy problem related around wetkit_core as most wetkit stuff depends on wetkit_core , but it seems to me that the only thing that wetkit_update depends on is "update" and I don't think any other wetkit module really "depends" directly on wetkit_update.

So , what are the implications of option 1 if any? a change to the install profile for the distro installation to add wetkit_update as default enabled? in order to maintain the current defaults without the dependancy hangups?

Option 3 might be:

  • add bunch of dependancy exclude to the other wetkit_ modules that depend on wetkit_core
  • seems like more work than option 1
nadine_cz’s picture

nadine_cz commented

I like Option 1 ...

I features_excluded wetkit_update in wetkit_core and was able to disable the wetkit_update and the update manager. We really can't use it here based on how our service provider builds our environments.

It would be great if the installation profile had a switch to toggle on/off (otherwise, we have to get our service provider folks to track another patch) - we are trying to keep that list as small as humanly possible.

sylus’s picture

sylus commented

Okay I am fine with Option 1 to but we will need to ensure the following use cases are met:

1) Option to deselect the wetkit update module during browser install (default will be enabled)
2) Option to deselect the wetkit update module during drush install (default will be enabled)
3) Ensure that current installs are not affected by the change

colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
commented
Issue summary: View changes
colan’s picture

colan
he/him
Primary language English
Location Toronto 🇨🇦
commented
Title: Performance optimization » Allow for the disabling of Update Manager
Issue tags: +Performance

More descriptive title & tagging.

sylus’s picture

sylus commented

Hmm this might be easier then I thought. Right now there is both a:

a) hook_install_n tasks for enabling wetkit_update in wetkit_core in wetkit_core_update_7104
b) dependency in wetkit_core for enabling wetkit_update

So we can just simply get rid of the dependency in wetkit_core thus having it enabled by default for fresh installations but easily abled to be turned off afterwards.

This seems like a sensible default to me.

sylus’s picture

sylus commented

Commit and atrribution to colan + joseph: http://drupalcode.org/project/wetkit_core.git/commit/df07c24

sylus’s picture

sylus commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

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

srikanth.g’s picture

srikanth.g commented

"drush dis update" command is working fine in my drupal 7.37 , but is there a way this module should be enable and the error messages are visible for a specific user(super admin) on Reports page only(not on all the drupal admin section pages)