House of Fusion
Search over 2,500 ColdFusion resources here
  
Home of the ColdFusion Community

Mailing Lists
Home /  Groups /  ColdFusion Talk (CF-Talk)

CFIMAGE Killing the Server

  << Previous Post |  RSS |  Sort Oldest First |  Sort Latest First |  Subscribe to this Group Next >> 
Top  |   Reply  |   Original Post  |   RSS Feed  |   Subscribe to this Group
Author:
Robert Harrison
05/07/2012 11:35 AM

A client has asked for the ability to upload multiple images at once. We've got that working. The images are also being to a large and standard view size using CFIMAGE. This is working also. Problem is when we upload a lot of images, CF falls behind in processing the CMIMAGE and it overloads the server whiles until it catches up... then everything comes back.   What is the best approach we can take to ensure we don't overload the server when doing this?  Would that be CFTHREAD or something? Any ideas? Thanks 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_

Top  |   Parent  |   Reply  |   Original Post  |   RSS Feed  |   Subscribe to this Group
Author:
Robert Harrison
05/07/2012 11:38 AM

> CORRECTION:  The images are also being resized to a large and standard view size using CFIMAGE 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_williams A client has asked for the ability to upload multiple images at once. We've got that working. The images are also being to a large and standard view size using CFIMAGE. This is working also. Problem is when we upload a lot of images, CF falls behind in processing the CMIMAGE and it overloads the server whiles until it catches up... then everything comes back.   What is the best approach we can take to ensure we don't overload the server when doing this?  Would that be CFTHREAD or something? Any ideas? Thanks 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_

Top  |   Parent  |   Reply  |   Original Post  |   RSS Feed  |   Subscribe to this Group
Author:
Raymond Camden
05/07/2012 11:42 AM

Here is a blog post on resizing options: http://www.raymondcamden.com/index.cfm/2008/11/1/ColdFusion-8-Image-Resize-options > >> CORRECTION:  The images are also being resized to a large and standard view size using CFIMAGE > > > Robert Harrison > Director of Interactive Services

Top  |   Parent  |   Reply  |   Original Post  |   RSS Feed  |   Subscribe to this Group
Author:
Robert Harrison
05/07/2012 11:58 AM

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_

Top  |   Parent  |   Reply  |   Original Post  |   RSS Feed  |   Subscribe to this Group
Author:
andy matthews
05/07/2012 12:46 PM

Are you informing the user when a specific image is rejected? 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_

Top  |   Parent  |   Reply  |   Original Post  |   RSS Feed  |   Subscribe to this Group
Author:
Robert Harrison
05/07/2012 02:44 PM

> Are you informing the user when a specific image is rejected? Yes. Of course.   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_

Top  |   Parent  |   Reply  |   Original Post  |   RSS Feed  |   Subscribe to this Group
Top  |   Parent  |   Reply  |   Original Post  |   RSS Feed  |   Subscribe to this Group
Author:
Byron Mann
05/11/2012 12:24 AM

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" <robert@austin-williams.com> wrote: ----- Excess quoted text cut - see Original Post for more -----

Top  |   Parent  |   Reply  |   Original Post  |   RSS Feed  |   Subscribe to this Group
Author:
.jonah
05/07/2012 04:14 PM

One thing I do if the source images are a lot larger than the destination dimensions is do a two-step resize. First, resize to 50% or 25% very quickly using highestPerformance, then go from that intermediate step down to the final size using highestQuality to get a nice looking image in much less time than doing highestQuality from the bigger original image. On 5/7/12 8:42 AM, Raymond Camden wrote: ----- Excess quoted text cut - see Original Post for more -----

Top  |   Parent  |   Reply  |   Original Post  |   RSS Feed  |   Subscribe to this Group
Author:
Raymond Camden
05/07/2012 11:41 AM

You are aware - I hope - that when you resize, you have something like 8 or so options for quality versus speed. Have you tried simply "moving down" to a faster, but less quality, resize? By default CF uses the best looking resize. Try something lower. That being said - yes - you could consider cfthread. You could also use a scheduled task that simply processes a 'chunk' of images from a directory every 15 minutes or so. ----- Excess quoted text cut - see Original Post for more -----


<< Previous Thread Today's Threads Next Thread >>

Search cf-talk

June 19, 2013

<<   <   Today   >   >>
Su Mo Tu We Th Fr Sa
             1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30             

Designer, Developer and mobile workflow conference