CiviCRM Community Forums (archive)

Recently, we met the same problem of civicrm + drupal exhaust much more memory. Every page need to allocate more than 40MB memory before deliver to client even if we use APC  or eaccelarator (before using, we need 100MB of memory).

So I go deep to watch some fat module / plug-in of drupal. Civicrm will make difference of 15-20MB to load after enable or disable civicrm.module.
Then I start to think why we need to initialize civicrm in every page? We don't want to boot ubercart in every page, because we don't need a shopping cart in whole site. Same with CRM, by the code of civicrm.module, I think only when we have block of civicrm / user page need to load civicrm. if we don't loading civicrm in every page, this will increase much performance in common drupal page, and when we need civicrm, it still there.

I start to trying this way, add a very little and dirty code to allow initialize civicrm only when such path:
function civicrm_initialize( ){
....
// when we would like to initialize ?
$allow_path = array(
  'user',
  'civicrm',
);
if(!in_array(arg(0),$allow_path)){
  return false;
}

// this does pretty much all of the civicrm initialization
$error = include_once( 'CRM/Core/Config.php' );

My question is:
Is something like this make sense for change civicrm.module to only allow some criteria then initialize civicrm?
Any potential risk or error on implement in this way?

hi Lobo,

Thanks for providing the patch. Confirm the your patch work for our case. Before apply the patch, memory usage need 33MB on every page. After that, only need 15-20MB on page load.

I'll apply this patch to an online site, to see if any problem there. As I know of Drupal, seems it make sense to remove these civicrm_initialize on hook_help.