Execution time is the time it takes for CF to compile the page, run the
queries and return results to be displayed. The time it takes a page to
show up is based on BW, clients machine settings/speed, and for the page to
display. Your execution time should always be as low as possible, so that
the page download time will not be to long. How fast is your execution
time?
These are for speeding up a page only, and not to be used in every case.
What can slow it down: CF Includes, lots of HTML, over modularity.
What can speed it up: Sticking all code for a high impact page into one
page. Caching queries. Limiting logic and variables. Less graphics. Less
HTML tables. Not calling cookies or client side variables. Less
JavaScript. Maintaining DB connection. A table structure specifically
written for the type of search their doing. Indexes.
>From CF 4.5 debugging:
Execution time = startup, parsing, & shutdown.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Karen Harker
Sent: Friday, January 19, 2001 12:52 PM
To: [EMAIL PROTECTED]
Subject: Cold Fusion Performance issues
I am trying to improve the performance of our most popular site for our
primary clients - a list of electronic journals (ejournals). Currently,
from on-campus (therefore, using campus internet connections, which are very
fast), the load time for the largest listings (for titles beginning with A
or J) averages 9 seconds. This is not very good. But it gets much worse
from off-campus (upwards of a minute).
The code is moderately complex (several conditionals determine exactly what
about each title is displayed) and heavily commented. There are also tiny
images that are displayed for each title. But I think the problem may simply
be the sheer number of records in the results set: for the A's there are 323
titles, and the J's there are 604. Multiply the execution of the code by the
number of titles, and it is no surprise it takes a while to load.
I'm trying to create potential solutions, but most of these ideas seem like
they may be too confusing to our clients. After some usability tests, we
have found that our clients (academic medical faculty, students and staff)
do not mind scrolling through a long list as much as they mind having
difficulties finding links that are "hidden" on separate pages. And the
alphabet browsing is still the most common way our clients find titles,
despite the long load time.
However, we would like to reduce the load time as much as possible. What
behind-the-scenes, technical tricks can I do to improve this?
Another thing - using "debug" mode, I get the "Execution time" in
milleseconds. However, when I use a hand-held timer, the average load time
is 3x the "Execution" time. What does "execution" time measure? Does the
difference mean that the problem is elsewhere?
Thanks for any help you can give me.
Karen R. Harker, MLS
UT Southwestern Medical Library
5323 Harry Hines Blvd.
Dallas, TX 75390-9049
214-648-1698
http://www.swmed.edu/library/
-------------------------------------------------------------------------
This email server is running an evaluation copy of the MailShield anti-
spam software. Please contact your email administrator if you have any
questions about this message. MailShield product info: www.mailshield.com
-----------------------------------------------
To post, send email to [EMAIL PROTECTED]
To subscribe / unsubscribe: http://www.dfwcfug.org
