If you've got Debug set on, take a look at the response time of the queries in theLinkUsage.cfm page... the issue might not be in your location action but in what the page is doing. If you're running SQL Server you might want to check for proper indexing on the tables involved... take one of the queries and run it through the execution plan in Query Analyzer and see what happens... if you see table scans then the DB is your culprit.

Good luck!
Hatton Humphrey

Karen Harker wrote:

We have been using a link hit counter to track which links our users are selecting. This involves passing a linkID number to a "linkUsage.cfm" template, that does these things:
1) Finds the right table (1/month) and creates a new one, if needed (i.e. the beginning of the month)
2) Inserts a row in this table
3) Finds the URL based on the linkID
4) Uses CFLOCATION to send the user on this URL.

Response time for such an application is getting too long (upwards of 10 seconds). I've tested the system up to the point of the CFLOCATION tag and the response times have averaged about 260 milliseconds (0.260 sec?), which seems reasonable. So that leaves the CFLOCATION tag as the potential reason for the slow response. Does anybody else have info about CFLOCATION and its potential slowness?
Does anybody else have a better solution?

Thanks.


Karen R. Harker, MLS
UT Southwestern Medical Library
5323 Harry Hines Blvd.
Dallas, TX 75390-9049
214-648-1698
http://www.swmed.edu/library/

-----------------------------------------------
To post, send email to [EMAIL PROTECTED]
To unsubscribe: Send UNSUBSCRIBE to [EMAIL PROTECTED]
To subscribe / unsubscribe: http://www.dfwcfug.org




-----------------------------------------------
To post, send email to [EMAIL PROTECTED]
To unsubscribe: Send UNSUBSCRIBE to [EMAIL PROTECTED]
To subscribe / unsubscribe: http://www.dfwcfug.org

Reply via email to