> page of queries that are each wrapped in a function. That
> udf file is then included in every page. We've got resource
> and performance issues but I've got the problem that
> management wants to forge ahead with things as is (while
> dealing with the performance issues) and I'm not able to
> explain things where it comes to performance. Can someone
> help me explain why one huge page with all your queries
> wrapped in a function is bad for performance. Or correct me
> if it's not bad.
If the functions aren't being called (and the queries aren't being run),
there shouldn't be too much of a performance hit involved in having them
included in every page. However, from an organizational perspective, that's
an awful way to manage your database interaction.
You can use CF's debugging and the GetTickCount function to see the impact
of including them in a page that doesn't use them.
> Also, there are so many little things that I wonder if it's
> hitting performance like the cfargument tags required
> attributes are all using 'true' or 'false' instead of 'yes'
> or 'no'. Would things like that cause a delay?
"True" and "Yes" are (mostly) interchangeable in CF, as are "False" and
"No". So, that shouldn't cause any performance problems.
In general, your best bet to determine application bottlenecks is the use of
load testing to see which pages run slowest, then the use of CF debugging
and GetTickCount within those pages to see what's actually running slowly.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
