Setup: Remove debug message for "caches"
This is currently forcing more object cache interfaces to be constructed
than might be needed in a given request. The configuration for these
interfaces is usually quite straight forward or can be trivially
verified from eval.php.
If we do want to log this, I would recommend doing it from the classes
constructor instead e.g. something like:
LoggerFactory::getInstance('MessageCache')->debug( get_class( $cache ) );
Bug: T189966
Change-Id: I06dc6dfbdf274bb57e9295b0c757b8d52c02acbe
This commit is contained in:
parent
582419334a
commit
70cb266480
1 changed files with 0 additions and 8 deletions
|
|
@ -789,14 +789,6 @@ if ( $wgCommandLineMode ) {
|
|||
$wgMemc = ObjectCache::getLocalClusterInstance();
|
||||
$messageMemc = wfGetMessageCacheStorage();
|
||||
|
||||
wfDebugLog( 'caches',
|
||||
'cluster: ' . get_class( $wgMemc ) .
|
||||
', WAN: ' . ( $wgMainWANCache === CACHE_NONE ? 'CACHE_NONE' : $wgMainWANCache ) .
|
||||
', stash: ' . $wgMainStash .
|
||||
', message: ' . get_class( $messageMemc ) .
|
||||
', session: ' . get_class( ObjectCache::getInstance( $wgSessionCacheType ) )
|
||||
);
|
||||
|
||||
// Most of the config is out, some might want to run hooks here.
|
||||
Hooks::run( 'SetupAfterCache' );
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue