We have an existing rails app that gets several million page views per day, and shortly we will be allowing users to upload image files. In the past I've made good use of eventmachine for stuff like this, creating specific purpose apps with eventmachine handlers. That worked, but it looks like merb would be a good choice now for stuff like this.
My main question is what would be the ideal deployment setup for an app that just handles image uploads and processing? I don't want to use apache, so passenger is out. I've seen merb supports thin, is that a good way to go? And since merb is thread safe, can you run a small cluster of merbs that can each handle several concurrent connections? From past experience I've found that you can't handle that many file uploads in a single ruby process. Ruby threads and the non blocking file io in ruby both use a select loop, and I've found that it effectively starts to block fairly quickly. But a cluster of merbs each configured to process up to 5 or so concurrent requests might work nicely, assuming it's possible to configure stuff this way. Any advice appreciated. Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
