That's actually a great idea!
Em qui, 26 de mai de 2016 4:04 PM, Matt escreveu:
> Check out node-canvas for the rendering, then you won't need any child
> processes.
>
> https://github.com/Automattic/node-canvas
>
> On Sat, May 21, 2016 at 8:20 AM, Zlatko Đurić wrote:
>
>> You should try it. Bu
Check out node-canvas for the rendering, then you won't need any child
processes.
https://github.com/Automattic/node-canvas
On Sat, May 21, 2016 at 8:20 AM, Zlatko Đurić wrote:
> You should try it. But the bottom line is, in a thousand-reqs-per-sec
> scenario, you'll almost always hit a bottlen
You should try it. But the bottom line is, in a thousand-reqs-per-sec
scenario, you'll almost always hit a bottleneck and need to scale the
processing job over multiple machines. So it's a tradeoff - how important
is it to you to finish every request, how fast you want results, is the
1k/sec throug
Interesting. I wonder if it is better to use phantomjs for the PNG
rendering. Although it is slower, I don't need child_process
On Fri, May 20, 2016 at 5:42 PM Zlatko wrote:
> You have multiple things there. Thousands requests (per second, I assume)
> is a lot even without spawning a child shell
You have multiple things there. Thousands requests (per second, I assume)
is a lot even without spawning a child shell. Thousands of spawned shells,
even without image magick, can bring a busy system down. But then again,
you will know best with a test. Try it and see if and where you get stuck.
