Closed (fixed)
Project:
Boost
Version:
6.x-1.18
Component:
Caching logic
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
9 Jun 2010 at 11:56 UTC
Updated:
20 Dec 2011 at 04:30 UTC
I have read the instructions, but am not sure if I should disable all of the core caching settings if i am using boost?
admin/settings/performance?
Comments
Comment #1
hixster commented** bump **
Comment #2
hixster commentedDo pages default to the Drupal standard cache settings if a registered user is viewing pages?
Comment #3
temp commented+1 Do i need disable core caching (/admin/settings/performance) when i use boost?
Comment #4
Gabriel R. commented+1
It is really not obvious if one needs to disable core caching (/admin/settings/performance) when using boost.
Comment #5
reswild commentedIf you are using boost for caching, the core caching should be disabled. You can find suggested settings for the /admin/settings/performance page here: http://drupal.org/node/545908#pg
My understanding is that neither Boost nor Core caching works for logged in users.
Comment #6
marios88 commentedOn my live sites i have core caching disabled, i dont know why this is recommended but i play it safe.
Still you can have cacherouter combined with APC/memcached for huge performance gains for logged in users and boost page cache generation
Comment #7
bisonbleu commented@marios88, it would be great if you could expand on how this can be done in a step by step way...
Comment #8
marios88 commentedsee http://drupal.org/project/cacherouter
install APC on your server if not there
read the manuals, pretty straight forward setup
Comment #9
bgm commentedAs reswild mentioned in #5, turning off core caching is the recommended way.
You can still turn it on, but it will not be very useful and might cause glitches since you then have two caches running at the same time (i.e. boost might generate a page using data that was cached, not the latest data).