16 Apr
2006
16 Apr
'06
10:30 a.m.
Well, being slower, doesn't at all imply that
it's too slow, so a
better question is in the overall rendering of a page, say a
complex edit form, what percentage of total rendering time is taken
by retrieving the description both cached and uncached. I mean, it
could be dwarfed by the call to goods(or whatever db you use) to
actually retrieve the objects, and if that's the case, running
uncached may not even be noticeable.
Yes, this is true, it won't be noticeable at least for building GUIs:
the description is only read once before visiting the descriptions
and building the interface. It becomes more of a speed problem when a
query is done over a graph with many described objects.
Caching may not be necessary at all, in the larger
scheme of
things, and frankly, I find myself flushing the cache constantly,
especially during development.
Why that? The cache is automatically flushed when descriptions change
in your code.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch