> 1. You say not saving the class files to disk "should only
> affect performance after a service restart, I think. I believe
> that CFMX caches compiled bytecode in memory in any case."
>
> But isn't the number of files cached in memory controlled by
> the template cache size? If thats right then when the template
> cache size is insufficient presumably a recompilation from the
> .cfm source will be necesssary if the class file hasn't been
> saved to disk.

Yes, that's correct. Of course, you should set the template cache size to a
sufficient amount so that you can cache everything you use regularly, at a
minimum.

> 2. Deleting the class files is somthing i'd rather not get
> into, just cos this feels a bit like a hack, and its
> something that occurs many times a day - 000's of editors
> updating their stuff. And besides, when i deleted the class
> files which were causing the problems (the ones related to
> the deleted .cfm files) it didn't fix the problem, presumably
> because it was also held in memory too.

Deleting class files has worked fine for me in the past. Once I've deleted a
class file, CF would recompile it on the next request in my experience. On
the other hand, I haven't had any problems with CF running a file after I've
deleted the cfm file itself.

Is each editor writing a separate cfm file? Do you have the "trusted cache"
setting enabled?

> 3. Quotes from live docs about template
> cache(http://livedocs.macromedia.com/coldfusion/6.1/htmldocs/b
> asicon5.htm):
> "For best performance, set this to a value that is large
> enough [...] yet small enough to avoid excessive reloading."
>
> Any idea what the "small enough to avoid excessive reloading."
> means?

Nope. I suspect that it means "don't waste memory you're not going to use",
but I don't know whether CF allocates memory up front for caching, or as it
uses it.

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]

Reply via email to