[thesite] query results caching

Seth Bienek seth at sethbienek.com
Mon Mar 5 10:44:14 CST 2001

Hi Rudy,

> excuse me, i hope i don't come across as whining, but nobody answered the
> last two times i asked this question...

Thelist traffic has grown so much that I don't get to read every message
like I used to.  Sorry `bout that.. The surefire way to get *my* attention
is to put CF in the subject line somewhere. :)

> why would you not use query results caching?

Query results caching is good for queries that do not change, as CF will
store a seperate copy of the query results for each *unique* query - not
much use if your queries are dynamic, and/or you have alot of them.  Also
there is a limit of 100 cached queries, though this may be tweakable.
Lastly, CF saves these stored query results as text files on the hard drive
instead of in the server's memory.  Not alot of performance overhead there,
but certainly more than getting the data out of the server's RAM.

For quick-and-dirty, or simple queries, query caching is probably the way to
go.  But if you are looking for a way to speed up access to large amounts of
data, or optimize a heavy-hitting dynamic query, the structure method's
good.  BTW, it is kind of a pain in the butt to set up; I think that's
something you have to weigh in the decision to implement it.

I just re-read that and I think I may have overcomplicated the explaination.
Lemme know if it's as clear as mud and I'll take another run at it.. :)


Seth Bienek
Solutions Development Manager
Stonebridge Technologies, Inc.
972.455.7294 tel
972.404.9754 fax
ICQ #7673959

More information about the thesite mailing list