I would personally turn that UDF file into a CFC, then invoke it with
CreateObject() instead of including it. Unfortunately, you'd have to
prefix your function calls with the object name you give it, but I think
this would be much less intensive on server load.

-Dain

[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

> I have inherited a CFMX application where there is a huge 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.  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?
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to