A dyno is the entire stack. A request, the second it hits Heroku, blocks a dyno. This could be because your application is processing, or because you are handling an upload.
If you are doing decent size upload, you should have your app upload directly to S3. Oren On Sun, Jan 16, 2011 at 12:33 PM, John Maxwell <jgwmaxw...@gmail.com> wrote: > Yeah - that is talking about the outgoing hop to S3 from Heroku - which is a > blocking I/O, not the incoming step into Nginx... Any word on this from an > official source? > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to heroku@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
