> 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"?
This should only affect performance after a service restart, I think. I
believe that CFMX caches compiled bytecode in memory in any case.
However, rather than disabling that feature, you can simply delete the
offending class file. It's usually pretty easy to figure out which one that
is by looking at the class file names, but if you can't, you can use this:
http://devilm.com/archives/000001.html
> 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.
If you have sufficient memory, I'd recommend that you simply put in the
number of cfm files you have. If you don't have sufficient memory, put in
the number that you run regularly as part of your application.
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]
