[support] how cache works: on the fly content creation (not node) and caching

[Ivan Sergio Borgonovo]

On Sat, 2 Jan 2010 14:26:02 -0600
Larry Garfield <larry at garfieldtech.com> wrote:

> > Actually for few tens of a second I was thinking to use ISAM just
> > for cache[1]... I wonder if this would become easier for D7. Yeah
> > I'm aware of fastpath... but I still meant *easier*.

> Actually, I'd go the other way.  In Drupal, the cache tables are
> one of the busier tables.  Cache, session, etc. are some of the
> heavier-write tables that you don't want to do table-level locking
> on.  watchdog or search indexes are good candidates for MyISAM,
> but not cache.

I was thinking about partitioning... but this make things much more
complex.

> Any time cache_clear_all() is called, anything that's not marked

When is cache_clear_all() called?

> Perhaps what you could do is just use your own cache table, and

But this can't exploit the fact that if a whole page is cached much
less php code is run.

I think I'll test the functional index and saving (url, external
data pk) in another table... and also collect more stats about how
pages are accessed to get an idea about where cache is needed.

Still being able to explicitly set $expire would be a big help.
The pattern I'm expecting may be actually better served by tuning
the expire time rather than flushing the cache when there is an
update... or even not caching at all some pages.

-- 
Ivan Sergio Borgonovo
http://www.webthatworks.it