Does anyone know how <cfcontent> handles file reads and memory? I am
concerned because of the lack of optimization using <cffile> for uploading
files. CF stores the files in memory until they are written to disk, and I
assume that they hold onto their process thread for the duration of the
upload -- both of which I would expect to adversely affect performance under
heavy load.
So for <cfcontent>, if the implementation is unoptimized (which seems
plausible given the limitations of <cffile>, which I assume are due to the
way CF integrates into web servers), I would expect that it:
- reads the .cfm page
- pulls the entire file from disk
- stores the entire file in CF server memory
- hands the web server (IIS) the entire file.
Here is a specific list of server concerns, which may help focus any
response:
1) memory usage
- unpredictable memory requirements
- fragmentation restrictions for large files on upload
- possible effects on CF's caching memory
2) Extended hold on process threads -- would 10 separate uploads by 28k
modems hold all 10 threads on a cf server for the duration of the uploads?
3) network bandwidth behind the firewall for file transfers -- are full
files are processed even for aborted downloads?
Thanks for any knowledge...
Matt
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body or visit the list page at www.houseoffusion.com
