Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How well does rails handle concurrent request when the controller is executing computation intensive tasks such as .wav to .mp3 conversion or image conversion tasks (or uploading of large files)? It is my understanding that frameworks such as .net handle this more efficiently, or?
conversions should be done in background jobs. Me and Github use Resque for that. The upload and other heavy I/O stuff is handled by NodeJS. You can enqueue a Resque Job via NodeJS.
So our setup looks like:
it’s completely non-blocking and the benefit of Resque is that you can access your whole Rails environment like Models, Helpers etc.
The actual conversion is done by native programs like ffmpeg etc. which we spawn in the resque job.