Try caching the results of cfdirectory in application scope i.e.

change:
<cfdirectory action="" directory="#vDir#" name="dirTest"
filter="z#fileIndex#.txt">
<cfdump var="#dirTest#">

to:
<cfif not isDefined("application.dirtest")>
<cfdirectory action="" directory="#vDir#"
name="application.dirTest" filter="z#fileIndex#.txt">
</cfif>
<cfdump var="#application.dirTest#">

This way cf only executes the _slow_ cfdirectory tag once (per application
cycle).

If the directory changes often (i.e. files get added, deleted, etc.,), then
I would run a job that periodically deletes the application.dirTest variable
and recreates it.  This way the processing overhead is still transparent to
the user.

I think you'll find i/o operations to be slow w/ any application server.

HTH


[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to