Posted by Jim on 07/16/07 09:30

> > If I could think of a way of doing it efficiently then I'd stick with
> > db only, but I can't see how. For example, I have a table which
> > represents the structure of the site, so to put it simply each record
> > has an id and a parent id. To build say a left hand nav I may need to
> > call 3 or 4 sql statements to get all the data I need which I'd like
> > to avoid doing if possible.
>
> Premature optimization?

Perhaps, but I'm still interested in the shared memory caching options
as there's more than once instance where I believe caching of data
would come in handy. At the moment I'm not seeing issues with with
performance, however on accessing a page I may have 5 or 6 db
statements accessing data which rarely changes (i.e. site structure,
data dictionary) and it feels like I'm making the db work un-
necessarily when the data could be cached. I need for the cms to be
able to scale well and I feel that ignoring caching would be a
mistake.

Jim.

[Back to original message]