From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.25.143.3 with SMTP id r3csp4216825lfd; Thu, 27 Aug 2015 00:06:34 -0700 (PDT) X-Received: by 10.50.110.103 with SMTP id hz7mr16271087igb.91.1440658872600; Thu, 27 Aug 2015 00:01:12 -0700 (PDT) Return-Path: Received: from mail-io0-x23e.google.com (mail-io0-x23e.google.com. [2607:f8b0:4001:c06::23e]) by mx.google.com with ESMTPS id rt10si26841igb.38.2015.08.27.00.01.10 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 Aug 2015 00:01:12 -0700 (PDT) Received-SPF: pass (google.com: domain of rack-devel+bncBD4PTDWJVIEBBNPL7KXAKGQEGSR6XQI@googlegroups.com designates 2607:f8b0:4001:c06::23e as permitted sender) client-ip=2607:f8b0:4001:c06::23e; Authentication-Results: mx.google.com; spf=pass (google.com: domain of rack-devel+bncBD4PTDWJVIEBBNPL7KXAKGQEGSR6XQI@googlegroups.com designates 2607:f8b0:4001:c06::23e as permitted sender) smtp.mailfrom=rack-devel+bncBD4PTDWJVIEBBNPL7KXAKGQEGSR6XQI@googlegroups.com; dkim=pass header.i=@googlegroups.com Received: by mail-io0-x23e.google.com with SMTP id s203sf7305255iod.1; Thu, 27 Aug 2015 00:01:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe; bh=SC5UIwDCfLsAJS45375mTxjpSFeaZ5vg1V30cCsu55g=; b=V/et+gN2/o6hfq9JTwkkI3QtmeI+8F+e/MRF4ulb9FbDVXePsbPJ3ZE3F8KPgLp3pA U/mdhl6i+7S85ZNTQEIKVI4jxsQNdm6itOPQlwe4qEbRgVVbf2/IYo+DZ0L8Q8uRf8Ur lyFCjGhQrUvQbW9VTsxVAqQOvcHeHrdlRzoSJJ7M/W9SPY/w4Wfmm+rpyQ0/DEt7BVPQ HtRE+smWRW2NRMqBdnVVqAzVPmoqYrcjgOs54f5Rm7/045xv2OxWMDhNKGpGZ1t8Wf85 /FFxnV/WLuJmS6qEUbLY0dv5K08xOIsP8XsdI7rr6/N5xqsITa++9D7t+kWHS+qdETHt HjHQ== X-Received: by 10.50.66.205 with SMTP id h13mr211137igt.10.1440658870100; Thu, 27 Aug 2015 00:01:10 -0700 (PDT) X-BeenThere: rack-devel@googlegroups.com Received: by 10.50.171.130 with SMTP id au2ls374666igc.34.gmail; Thu, 27 Aug 2015 00:01:09 -0700 (PDT) X-Received: by 10.107.170.212 with SMTP id g81mr7333801ioj.19.1440658869448; Thu, 27 Aug 2015 00:01:09 -0700 (PDT) Received: from dcvr.yhbt.net (dcvr.yhbt.net. [64.71.152.64]) by gmr-mx.google.com with ESMTP id lp10si167118pab.1.2015.08.27.00.01.09 for ; Thu, 27 Aug 2015 00:01:09 -0700 (PDT) Received-SPF: neutral (google.com: 64.71.152.64 is neither permitted nor denied by best guess record for domain of e@80x24.org) client-ip=64.71.152.64; Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id E6CA21FD1F; Thu, 27 Aug 2015 07:01:08 +0000 (UTC) Date: Thu, 27 Aug 2015 07:01:08 +0000 From: Eric Wong To: rack-devel@googlegroups.com Subject: Re: Rack and memory usage ? Message-ID: <20150827070108.GA4011@dcvr.yhbt.net> References: <9d5cc646-0803-42c3-b118-f54a4cf8c6c0@googlegroups.com> <1440276882101.d5f8b2d3@Nodemailer> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline In-Reply-To: X-Original-Sender: e@80x24.org X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 64.71.152.64 is neither permitted nor denied by best guess record for domain of e@80x24.org) smtp.mailfrom=e@80x24.org Reply-To: rack-devel@googlegroups.com Precedence: list Mailing-list: list rack-devel@googlegroups.com; contact rack-devel+owners@googlegroups.com List-ID: X-Spam-Checked-In-Group: rack-devel@googlegroups.com X-Google-Group-Id: 486215384060 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , James Tucker wrote: > Well since YARV and the various GC tunings it's got a lot more heavy > actually, and a lot more overhead and so on have landed in the stdlib (e.g. > "packaged gems" and so on). This has a lot to do with the fact that the > bulk of users for a long time have been running fat applications (e.g. > rails). Yeah. Lots of the GC speed improvements (lazy sweep, generational GC) lead to increased memory usage. We've been trying to fight back in ruby-core and getting ordering removed from non-Hash stuff might promising for 2.3: https://bugs.ruby-lang.org/issues/11414 https://bugs.ruby-lang.org/issues/11420 Lately, working again in Perl5 has gotten me to appreciate the control afforded by reference counting :) -- --- You received this message because you are subscribed to the Google Groups "Rack Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout.