Seems like something whose practicality can be easily tested. Pick a
commonly run query and set it up to cache. In CF Admin tell CF to cache up
to 10 unique queries. Watch memory usage on the server. If memory usage is
still well within limits, try setting the limit to 20. Repeat as desired.
I use query caching quite a bit (with CF 4.0x) and have yet to pull back
because of memory concerns.
You can argue that caching may result in needing fewer simultaneous
connections to the DB; each of those connections cost memory too..
-----Original Message-----
From: Todd McFarlin [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 18, 2000 1:08 PM
To: CF-Talk
Subject: CFQuery and Caching
Greetings all,
I am new a this project and the current methodology doesn't utilize
query caching. I attempted to make an argument, but could not satisfy the
big man's concerns of memory consumption.
The project is an app, so I cannot quote the configuration that it will run
on.
The largest query result would pull 1000 rows*15 columns.
Can any offer advise to an argument? Pro or Con:
TIA,
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
