> The overhead is most likely on the cache file writes
> and cache reads. You just gave me an idea for a work
> around that could be better and faster than all the
> options we have just discussed. With both ISAPI and
> CFX, the system has to compress each and every single
> page output as it is a new one. Might as well store the
> compress data into the db using CFX_GZip and serve it out
> of the database. This way, not only do we save CPU time
> we also save I/O overhead. Serving from the database is
> much more efficient (ram and cpu wise) in the long run
> than reading from the filesystem. So we only compress
> it once every so minutes or hours.
Hmmm... Very interesting...
I was considering decrupting CFCACHE and using this bit of code in there.
Using the DB instead... That has some promise... I may have a project to
play with....
Why cache DB queries when you can cache the entire page result that was
based on the query, right?
My only concern is that CF seems to be very unfriendly to binary data. I
wonder if there is any way that you could get the binary GZIP data back out
of the DB and serve it to the browser without needing to save it to a
temporary file and use CFCONTENT to send it out. If that does indeed pose a
problem, then perhaps hacking up CFCACHE might be the only solution.
> > > With IIS 4.0 you need the recource kit which contains the
> > > isapi compression filters.
> >
> > Ahhhh.... Now this I did not know... I must give this a try...
>
> Look for compFilt.dll and gzlip.dll and deflate.dll
Will do. Thanks!
Best regards,
Zac Bedell
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
