If you run it with "nice" to lower the cpu priority you should have no problem. We are doing the exact same thing with imageMagick and ffmpeg. We aren't in production yet but it looks good in testing. With a lot of conversions running the cpu pegs at hundred percent, but the pages serve fast anyway.
On Fri, Feb 3, 2012 at 8:57 PM, Angelo Chen <angelochen...@gmail.com> wrote: > Hi, > > I use ExpressJS for file uploading, after that, pass the files to node- > imagemagick to resize, if we got 100 files uploaded, the entire cpu > will be committed to various convert child processes, and entire site > become unresponsive during this process, the server is a I5 processor > with 8G memory running 64 bit Centos. > > what is the good practice for this? can we use one core of the CPU to > do conversion so site can still be responsive? or we can serialize the > conversion to limit to 2 or 3 at one time? any suggestion will be > appreciated. Thanks, > > Angelo > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
