I've got an app which makes heavy use of dynamically created cfm files - created when a page is requested for the first time and the cfinclude fails, and deleted when the underlying data is changed. The next time the page is requested the cfinclude fails and the file is re-created.

I've had a problem on a live server where I deleted a .cfm file, but MX continued to "use" it, presumably because it was still using the compiled .class - "save class files" was set to true on the CFadmin caching page.
I seem to have resolved the issue by not saving the class files, but i was wondering what impact this is going to have on performance.
Is this a known "feature"?

Also, what value should i use for "template cache size"? There seems to be a discepancy between what CFadmin says, and what i've found on live docs. My app has around 50,000 .cfm files - about 2500 handmade, and the rest dynamically created.

CFadmin:
"you can achieve optimum performance by setting this value to the total number of all of your ColdFusion templates"

http://livedocs.macromedia.com/coldfusion/6.1/htmldocs/basicon5.htm:
"For best performance, set this to a value that is large enough to contain your application's commonly accessed ColdFusion pages, yet small enough to avoid excessive reloading."

TIA
Bert

ps running CFMX6.1 on JRun, win2k
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to