From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: large uploads
Date: Thu, 29 Sep 2011 18:47:11 +0000 [thread overview]
Message-ID: <20110929184711.GA21222@dcvr.yhbt.net> (raw)
In-Reply-To: <CAOf2Z5t0pPf8-9mvnn8T=ep-uiUed-nkvoBdKk+yajqCXDFw=w@mail.gmail.com>
John Joseph Bachir <j@jjb.cc> wrote:
> My application accepts uploads from users, which can be quite huge in
> some cases. This of course requires setting the unicorn timeout to
> something much higher than 60 seconds, more like 10 minutes.
>
> Are there any drawbacks to doing this, other than the obvious drawback
> of not killing off long-running requests that are illegitimate?
Are your users remote? (outside of your immediate LAN).
The upload speed (and thus timeout) for unicorn should be based on
the nginx <-> unicorn transfer rate. Unicorn should never talk to users
directly and users can upload slowly to nginx which buffers requests to the
filesystem, first.
> I've googled quite a bit about this and have found surprisingly little
> -- I guess people who have apps that receive uploads just generally
> don't use unicorn?
I have a LAN-only application that regularly processes uploads several
hundreds of megabytes (via PUT) directly to Unicorn. The local disk I/O
is often the limiting factor since the parallel requests fill up the
kernel buffers and wait on disk I/O. The Rack application itself
unfortunately needs to seek/rewind so it must be in the filesystem.
Rainbows! with ThreadSpawn/ThreadPool can process uploads without
buffering them to disk first (but the Rack multipart parser may not).
I often stream several hundred megabytes of data directly to apps on
Rainbows! via PUT requests (curl -T), too.
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2011-09-29 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 18:28 large uploads John Joseph Bachir
2011-09-29 18:47 ` Eric Wong [this message]
2011-09-29 20:05 ` John Joseph Bachir
2011-09-29 20:54 ` Eric Wong
2011-10-01 3:39 ` John Joseph Bachir
2011-10-01 4:06 ` Eric Wong
2011-09-29 20:58 ` Justin Giancola
2011-09-29 18:48 ` cliftonk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110929184711.GA21222@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=mongrel-unicorn@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).