Why do filter cache entries expire 24 hours after last cron?
I'm putting together an overview of Drupal's various caching mechanisms. I'd like to put the answer to this question in there. Thanks. -- Prometheus Labor Communications, Inc. http://prometheuslabor.com 413-572-1300 Communicate or Die: American Labor Unions and the Internet http://communicateordie.com
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Steve Dondley schrieb:
I'm putting together an overview of Drupal's various caching mechanisms. I'd like to put the answer to this question in there.
Filtered items are expired in order to keep the filter cache from outgrowing your hard disk. Since Drupal's filter is "dumb" in the sense that it doesn't know on which node the filtered item depends, this is the only way to make sure the cache isn't full of old data. On drupal.org I've modified this to keep the cached items for 48 hours. Last time I looked the cache table had about 250k entries. Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFH8Jhyfg6TFvELooQRAnJgAJ9Ct4Qc6I+BMq5rLNteO05XI3ZGfgCfcY4a ORoCukQjZsls/OH5Y1aH1Sg= =jn0Y -----END PGP SIGNATURE-----
On Monday 31 March 2008, Gerhard Killesreiter wrote:
... Since Drupal's filter is "dumb" in the sense that it doesn't know on which node the filtered item depends
Gerhard, I'm sure you recognize this... There's nothing "dumb" in not linking the filter cache to nodes. Filters apply to other objects, like blocks, and AFAIK there's no hook_blockapi() to tell the filter cache when a block gets deleted, updated, etc... I'm just pointing that this is not simply an oversight. -Dave
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dave Cohen schrieb:
On Monday 31 March 2008, Gerhard Killesreiter wrote:
... Since Drupal's filter is "dumb" in the sense that it doesn't know on which node the filtered item depends
Gerhard, I'm sure you recognize this... There's nothing "dumb" in not linking the filter cache to nodes. Filters apply to other objects, like blocks, and AFAIK there's no hook_blockapi() to tell the filter cache when a block gets deleted, updated, etc...
I'm just pointing that this is not simply an oversight.
Of course it isn't. That's why I put the quotation marks around dumb. Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFH8RlCfg6TFvELooQRAt1bAJ42FrbFTpmOaTtKUOqLDWbr6DlIOQCdEshh m9ZVoJhGSSstkXgVP403epE= =QRwN -----END PGP SIGNATURE-----
participants (3)
-
Dave Cohen -
Gerhard Killesreiter -
Steve Dondley