> -----Original Message----- > From: Simon Horwith [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 01, 2003 10:47 AM > To: CF-Talk > Subject: RE: loopy loop! > > > file I/O operations are very fast - their speed tends to be > under-estimated by developers. One thing you should watch > out for are concurrency issues... I recommend using named > locks whenever accessing the local file system.
If your process is taking several hours you may be able to speed things up considerably by doing your initial I/O on a RAM drive. In general for huge jobs like this writing directly to the file system faster because CF does not have to maintain memory space for the entire result. However it's still hamstrung (a little) by the physical speed of the disk. In many corporate environments write-ahead caching is not allowed for data integrity issues - this will really kill peformance if you're used to having it turned on (often the case on a developer's local machine). A RAM disk effectively eliminates the physical disk lag, but maintains the "append and forget" speed of direct-to-file processing. Once you're done a single file operation moves the file from the RAM Disk to the physical disk. Very peppy. Jim Davis ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
