> We run a windows scheduled task to delete class files in
that folder that are
> older than a couple of days. I'm currently looking for a
better solution...
> typically we have > 15,000 files in there at any one
time (that's with clearing
> out files that are older than 2 days!).
You can switch them off completely in CFAdmin. They serve
very little
purpose, and apparently slow things down on large
applications, a CF has to
to a directory scan each time a template is called to see if
the class file
is up to date. I don't imagine the directory scan is such a
problem on
*nix systems, but it's slow on Windows once one has more than
a few hundred
files in a directory (in my experience).
The only performance hit you will receive if you don't bother
saving them
is that the application will be slightly slow after a CF
restart, as it
recompiles all the source code (which thenceforth is held in
memory). The
only thing the class files are for is to reduce the first
compile time:
they're a hindrance after that.
As you should not be doing CF restarts on a production
server, there's no
benefit in saving them. And I find CF gets confused sometimes
between
which is more up to date - source code or class file -
anyhow, so it can
cause issues in a dev environment too.
--
Adam