Yes, Ray's tag also stores things in memory (in fact I think CFACCELERATE
was based on Ray's tag). What I meant to say regarding performance was that
when Brandon (and Ray as well I beleive) testing their in-memory caching
against CFCACHE, the difference in speed was measured in orders of
magnitude. So basically, cache to memory as much as you can. (Obviously, use
your head and don't kill your server though.)

On 9/21/07, Dave Watts <[EMAIL PROTECTED]> wrote:
>
> > I'm not sure, but if I recall correctly CFCACHE still writes
> > temp files to the file system and reads them back each time,
> > which doesn't perform very well under load.
>
> Actually, reading the files from disk does perform quite well under load.
> It's creating the files in the first place which is the problem, since
> this
> is done by running CFHTTP to request the file. In effect, the first
> request
> takes twice as long as it otherwise would.
>
> > Have a look at Ray's scopecache custom tag.
>
> I haven't used Ray's tag, but in a similar vein I'd strongly recommend
> Brandon Purcell's CF_ACCELERATE custom tag:
>
> http://www.bpurcell.org/blog/index.cfm?entry=963&mode=entry
>
> Instead of writing to the filesystem, it stores entries in memory.
>
> Dave Watts, CTO, Fig Leaf Software
> http://www.figleaf.com/
>
> Fig Leaf Software provides the highest caliber vendor-authorized
> instruction at our training centers in Washington DC, Atlanta,
> Chicago, Baltimore, Northern Virginia, or on-site at your location.
> Visit http://training.figleaf.com/ for more information!
>
>
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Get involved in the latest ColdFusion discussions, product
development sharing, and articles on the Adobe Labs wiki.
http://labs/adobe.com/wiki/index.php/ColdFusion_8

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:289136
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4

Reply via email to