>>>Thanks! In an entirely different Structure/Cached Query application
comparison from the one where I earlier today posted the code here,
I'm seeing Structures are still 15% slower.
Without doing tests, I believe this is going to be the case. Structures are
more efficient for storing and managing data, but aren't necessarily the
fastest for looping or outputting that data because query result sets are
simple grids which are very easy for an application server to run through.
>>>Dave Watts opined here that he didn't believe there really was a
limit to how many queries CF would cache, the CF Administrator/Settings
Statement that: "The maximum number of cached queries allowed at any given
time is 100."
>>>notwithstanding. (I notice CF4.0.1 accepted my limit of 9999 but not
10000. Is there a message here?)
I posed this question directly to Jeremy Allaire a few weeks ago and he said
that there was not a limit on the number of cached queries. The 100 is
misleading. He said as long as you have RAM, you can cache queries,
although as this number gets larger and larger, your server may slow
slightly as it tries to manage all this information. So just exercise good
judgment and don't try to cache everything, just because you can. Cache it
if it benefits the application.
>>>So IF the CF limit on Cached Queries is not limiting to your application,
and IF Cached Queries are faster than Structures, then it's starting to
look like Structure NYET, Cached SI. NO?
I would tend to agree although I really don't do a lot with structures. So
someone else that's a structure fan might have evidence to the contrary.
Running through queries is a very simple looping operation. Parsing a
structure would inherently take at least a little more effort. Whether
that's noticible would probably depend on the structure model itself and the
server executing the code.
>>>I guess it's possible in a very active site for Cached Queries to require
more ram then Structures. This consideration might require monitoring to
establish the appropriate timeout for the Cached Queries.
Again, as long as you have the RAM, you're using the queries for a
beneficial purpose, and you have them expire at a reasonable time, you
shouldn't have "memory overload" and your application and server should stay
lean and efficient.
That's my two cents. Anybody else want to jump in??
--Doug
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
