Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Single use forks

Received: by 10.180.94.105 with SMTP id db9mr201087wib.2.1334877547951;
        Thu, 19 Apr 2012 16:19:07 -0700 (PDT)
X-BeenThere: python-tornado@googlegroups.com
Received: by 10.180.78.134 with SMTP id b6ls413300wix.4.canary; Thu, 19 Apr
 2012 16:19:01 -0700 (PDT)
Received: by 10.180.93.68 with SMTP id cs4mr199832wib.3.1334877541703;
        Thu, 19 Apr 2012 16:19:01 -0700 (PDT)
Received: by 10.180.93.68 with SMTP id cs4mr199831wib.3.1334877541694;
        Thu, 19 Apr 2012 16:19:01 -0700 (PDT)
Return-Path: <spence...@gmail.com>
Received: from mail-wg0-f49.google.com (mail-wg0-f49.google.com [74.125.82.49])
        by gmr-mx.google.com with ESMTPS id ca1si192210wib.1.2012.04.19.16.19.01
        (version=TLSv1/SSLv3 cipher=OTHER);
        Thu, 19 Apr 2012 16:19:01 -0700 (PDT)
Received-SPF: pass (google.com: domain of spence...@gmail.com designates 74.125.82.49 as permitted sender) client-ip=74.125.82.49;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of spence...@gmail.com designates 74.125.82.49 as permitted sender) smtp.mail=spence...@gmail.com; dkim=pass header...@gmail.com
Received: by wgbdr1 with SMTP id dr1so6758069wgb.30
        for <python-tornado@googlegroups.com>; Thu, 19 Apr 2012 16:19:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        bh=atxrn4qD47rkWHX5oEP2bAr2Ia1ZC84edbZ2EqC8jkg=;
        b=P1SkmhNTzaE2Kv/cU36rIisvJRyhyn+EgKt8z06Q7oXIhYME9a0w6+NOLurCbkti+e
         g3tXHxiA2I0bExi/fLt/zNvQY4ql54e+o6qicAZOWxwS0/yJPq8EDRoFjUatkWIYIxgV
         DUIuKMs/uPrPST+5VFJCg/xx+yzxM5t900/UHQUhXZBFuNsNhyTDIZf/P7Jfgzhl+g3a
         VTUP0dkTJGYRIeUnZwiON08mjeT54pSq14DtwxrvoKvC2hEQozzj6mNyeER/a14l6IWg
         f/aGy65i/a7/w1q/+kZw/2t22DG2cV6eJ9aUL2lpJQ0rQkxKmRhNHNBwWk7pFnTo3dB4
         76rA==
MIME-Version: 1.0
Received: by 10.180.73.143 with SMTP id l15mr9581990wiv.11.1334877541404; Thu,
 19 Apr 2012 16:19:01 -0700 (PDT)
Sender: spence...@gmail.com
Received: by 10.223.155.134 with HTTP; Thu, 19 Apr 2012 16:19:01 -0700 (PDT)
In-Reply-To: <be632934-31c4-4d3a-9b70-724d98bf0...@qd3g2000pbb.googlegroups.com>
References: <be632934-31c4-4d3a-9b70-724d98bf0...@qd3g2000pbb.googlegroups.com>
Date: Thu, 19 Apr 2012 15:19:01 -0800
Message-ID: <CANmUDYseKJHw1V9fGP2=ghoUSdLtjdf1=XUG3tbKscO7m6v...@mail.gmail.com>
Subject: Re: [tornado] Single use forks
From: Shane Spencer <sh...@bogomip.com>
To: python-tornado@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1

I have found appreciation of inetd for this task.

On Wed, Apr 18, 2012 at 9:49 AM, SDQL <joe.sportsdatab...@gmail.com> wrote:
> Hi,
>
> Is it possible to use a new fork for each client request?
>
> My problem is that some client requests require a lot of RAM which is
> not recovered after the request finishes.
>
> Thanks in advance for any clues!
>
>
> Joe