Lets put it this way, an archive thread can be 1 or more messages. Lets say that for some threads, this is 50 messages. These have to be retrieved from the DB, sorted using a maketree sort and then displayed. Now I have a new maketree sort that's fast and smooth as hell, but it still takes time and processing. On the other hand, if I do the processing once when a message is added to the thread, it never has to be done again. If I write a funky save mechanism so that there are no more than 1000 threads saved in a directory and directories are created on the fly, I can have the physical files spread out over a bit of space and the savings of a flat file.
> What are the advantages of storing articles and archived list messages in > individual text files? Even without the CFINCLDE caching issues, that's a lot > of disk files. > > Jim > > ----- Original Message ----- > From: "Michael Dinowitz" <[EMAIL PROTECTED]> > To: "CF-Talk" <[EMAIL PROTECTED]> > Sent: Sunday, July 07, 2002 1:30 AM > Subject: MX Caching > > > > Here's an interesting issue. > > Basically, when a CF page is run in MX, it creates a class file for that > page. This class file is stored in a single directory. If the page happens to > use CFINCLUDE, then that CFINCLUDE is also stored in the classes directory. > This goes on and on over ALL pages run through MX. The end result is a > directory full of class files that are basically a cache of all the CF > templates on your machine that have been run. > > Now this isn't so bad till you come to publishing sites (like Fusion > Authority). The standard technique is to store an article as a flat file and > put a pointer to it in a DB. When a page is run that references the article, > the flat file is included into the page. This can result in a LOT of class > files. An average issue of FA will have 20 includes, one for each story. The > same goes for the archives on CF-Talk and the other lists. Lots of includes. > And if your running a multi-homed site, all of the templates and includes for > ALL of the sites are in that one directory. > > Does anyone know a way of spreading this out some? Some JRun setting that'll > allow multiple classes directories or a classes directory that does some sort > of sub-directory creation? Maybe even a setting to allow each multi-homed site > to have its own classes directory? > > ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
