> BY ID DESC
> Any query whose debug output exactly matches this debug
> output will take advantage of the statement pool.
> IN CFML, it is fairly unusual for SQL statements to
> exactly match, unless <cfqueryparam> is used extensively.
> This means that statement pooling is unlikely to be
> helpful in most CFML apps.
> Even when statement pooling gets frequent matches, the
> performance gains are likely to be very modest unless the
> SQL text is very long and parsing it represents a
> significant effort."
My own applications use a structured method of generating sql syntax,
so I guess the likelyhood of producing identical debug output in my
case is greater... and given that cfqueryparam is automatically
applied to all variables and nothing is said about the name of the
query _and_ that the query component uses the same name for all the
queries anyway I guess the odds of this happening increase some...
Although oddly enough, I have yet to see it happen, even in the midst
of database changes. I suppose that doesn't mean it won't. :) But
given all the information I'd have to say that I'd consider setting
max pooled statements to 0 a best practice. In cases where caching (of
any kind) is needed for efficiency, caching the query (either natively
or in memory) is bound to be far more effective than any gains the
statement pool will render.
s. isaac dealey 954.927.5117
new epoch : isn't it time for a change?
add features without fixtures with
the onTap open source framework
http://www.sys-con.com/story/?storyid=44477&DE=1
http://www.sys-con.com/story/?storyid=45569&DE=1
http://www.fusiontap.com
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
