For cpu intensive tasks like this it would probably be good (if possible) to off-load the image resizing to non-public facing machines.
I would do something like upload the files to a share and in the background have non-front end server(s) handle the image processing. For our internal apps we have 4 CF machines that handle most user related tasks, then we have an isolated machine/instance that runs some of the more cpu intensive tasks, so users don't see the adverse effects. Depending on your volume of images, you might also want to look at other image processing alternatives that may handle the load better. Byron Mann Lead Engineer and Architect Hostmysite.com On May 7, 2012 11:59 AM, "Robert Harrison" <rob...@austin-williams.com> wrote: > > We found the problem. It was choking on CYMK images. We're now rejecting > CYMK images and it's working. > > We're allowing the user to upload multiple images at once (maybe even 50), > then resizing as needed using CFIMAGE. Works fine when you put in a reject > for CYMK images. CFIMAGE does convert the CYMK to RGB, but that apparently > requires significant processing resources. > > Robert Harrison > Director of Interactive Services > > Austin & Williams > Advertising I Branding I Digital I Direct > 125 Kennedy Drive, Suite 100 I Hauppauge, NY 11788 > T 631.231.6600 X 119 F 631.434.7022 > http://www.austin-williams.com > > Blog: http://www.austin-williams.com/blog > Twitter: http://www.twitter.com/austin_ > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:351115 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
