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 memor
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 any
Hi Angelo,
This sounds like a serious 'general principle' question rather than an
"arggh help" question so I'm sure you're already aware of this, but for the
sake of archive posterity I feel like I should mention using a third party
service e.g. Transloadit for this sort of job.
I've tried using
> [Disclaimer: My third client implementation makes me a serial customer of
theirs. I would probably stick a Transloadit sticker on my laptop so I
guess that makes me a fanboy]
Thanks : ). Glad to hear our service is working well for you!
For those determined to engineer their own solution, her
> I still have nightmares from the last time I used CentOS
+1
--
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
On 5 February 2012 00:50, Felix Geisendoerfer wrote:
> Use Amazon S3 as a temporary file system: When you get a new file, put it
> there (use reduced redundancy if you want to save costs), then let the
> workers pull the file from S3. You will thank yourself for doing this when
> it comes to scali
