From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Status: No, score=0.8 required=3.0 tests=AWL shortcircuit=no autolearn=unavailable version=3.3.2 X-Original-To: unicorn-public@bogomips.org Received: from mail-qg0-f52.google.com (mail-qg0-f52.google.com [209.85.192.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id BEA7A1F5AF for ; Fri, 6 Jun 2014 15:13:08 +0000 (UTC) Received: by mail-qg0-f52.google.com with SMTP id a108so4618341qge.39 for ; Fri, 06 Jun 2014 08:13:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=VfNuqfKusyDJm4/OKYv8r9DwuDD7vqe2TBNd1SI5V0M=; b=N6NkAnkJY1ah3iJbElk72qo99fXQ8l9h+CRDVauT1zu4YRMCX7IbmNs5zusNK6JZrj OF18YJTNHctqky4KTHRfCzLhIkVe5wycFUev6oIV622Lia6KFqkn6EtvEgbreVNvohuT Hw7XK52tEBjtTVf417D30/1tGTb9vp406G0erjH0dgYPbbbxz+H3wnAK+vQ/svcTg1tW G4xG3uDee1vxs/oNWvelYvlbJwOj2M4G4RVB80WwaiP6qcGuyt09CR83PfZvCzyvGMiQ NsdU8Pp+Regq3miEN+x3Tdn/+BMADetj6lp7sal77V7pOsM3VzXeo9f9lcjb06e5tAr+ RxGA== X-Gm-Message-State: ALoCoQmnxakxRQJlpgJqaWFvF4CkEKpb57cf8OPuuUB3QgFlH51wclWAwwxLgYvK/IPDE+BKgnId MIME-Version: 1.0 X-Received: by 10.224.46.66 with SMTP id i2mr9935151qaf.22.1402067587789; Fri, 06 Jun 2014 08:13:07 -0700 (PDT) Received: by 10.140.102.236 with HTTP; Fri, 6 Jun 2014 08:13:07 -0700 (PDT) In-Reply-To: References: <20140606012737.GA29097@dcvr.yhbt.net> Date: Fri, 6 Jun 2014 08:13:07 -0700 Message-ID: Subject: Re: Dealing with big uploads and/or slow clients From: Michael Fischer To: =?UTF-8?Q?Br=C3=A1ulio_Bhavamitra?= Cc: unicorn-public Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: On Fri, Jun 6, 2014 at 6:31 AM, Br=C3=A1ulio Bhavamitra wrote: > So the idea is that nginx will buffer the upload request until all > data is received and then it will send it to unicorn? So unicorn only > receives the full request? Should I do some configuration to nginx for > this? Yes; there are a few tunables worth looking at. The "Buffers" section here offers some useful discussion: https://www.digitalocean.com/community/articles/how-to-optimize-nginx-confi= guration Best regards, --Michael