Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Does the image processing happen in a child process in node? I'm curious how your code does the heavy CPU without blocking node's main thread.


Yes image processing happens in a child process.

Right now I'm using GraphicsMagic resource limiting flag -limit for preventing it from taking down all the resources.


Would what you're doing right now be possible using canvas on the client side?

On second thought, that might make things much more complicated / slow, you'd have to write something that allowed clients to send back processed results to speed things up for future searches by other users.

I wonder if there's any desire for something like http://maprejuice.com/, but easily applicable to any processing task that needs to happen in realtime * , as mentioned in the previous paragraph.

* But also support cached results.

PS If/when your no.de server crashes, do you have to push again to get it to restart? I was having this problem the other day — it's annoying to have to add a space to a file, commit and push just to restart the server.


I'm sure this can be done using Canvas. I might give it a try as a learning exercise in the future. Thanks for the suggestion :)

Didn't know MapRejuice, looks promising.

Regarding no.de, I have the same issues you describe. I'm looking forward moving to a larger SmartMachine where I can deploy using capistrano.


Cool. I noticed you're using Joyent too. I'm just starting a personal project on my own no.de smartmachine I got a few months ago.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: