Not knowing what your query is doing and also not knowing what the original
query result set is and its properties makes this a difficult question to
answer. Both of the links you provided seem to generate on html output so I
can't see any debug info but what I will say is that they both took aroun
The second link for me did take a noticeably longer time to load than
the first. The first kind of came up almost immediately.
On Tue, 8 Feb 2005 03:12:12 -, Paul Vernon
<[EMAIL PROTECTED]> wrote:
> Not knowing what your query is doing and also not knowing what the original
> query result se
> The second link for me did take a noticeably longer time to load than the
first. The first kind of came up almost immediately.
Strange, I tested 2 or 3 times and it was about the same... I test now and
there is a marked difference My comments however still stand. Without
knowing how big the
I agree that it is hard to answer the question, just wanted to point
out that I was noticing the differences in speed.
On Tue, 8 Feb 2005 03:31:09 -, Paul Vernon
<[EMAIL PROTECTED]> wrote:
> > The second link for me did take a noticeably longer time to load than the
> first. The first kind o
Try the 2 links again.
I had forgotten that cfttrace doesn't work unless you have debug priveledges.
Ive populated the execution times for the qoqs during runtime and used
cfflush to spit them out in realtime
Here is the app running on 6.1 (same server)
http://eureka.ext.usu.edu/spider.cfm?q=61&
Those times look like overheads to me... Out of interest, how big is your
original dataset? Do these times differ significantly if the size of the
result set changes? How wide is the result set and how many rows does it
have in general?
The next thing to ask is Is there a good solid reason wh
LOL, i found out what it was.
You can specify 'columntypelist' in the queryNew function. Its
optional, but not specifying any data type put a significant increase
in load time.
Insteresting.good to know.
On Mon, 7 Feb 2005 21:21:33 -0700, Jay McEntire <[EMAIL PROTECTED]> wrote:
> Try the
That sounds like a new "best practice" - always specify a columntypelist for
CF7 queryNew() calls.
-Original Message-
From: Jay McEntire [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 8 February 2005 12:30
To: CF-Talk
Subject: Re: CF MX Performance Hit -- Amy I the first to notice
Message-
>From: Jay McEntire [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, 8 February 2005 12:30
>To: CF-Talk
>Subject: Re: CF MX Performance Hit -- Amy I the first to notice? QoQ
>
>LOL, i found out what it was.
>
>You can specify 'columntypelist' in the queryNe
9 matches
Mail list logo