From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23231 invoked by alias); 20 Nov 2012 22:10:51 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 30810 Received: (qmail 17747 invoked from network); 20 Nov 2012 22:10:39 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 Received-SPF: neutral (ns1.primenet.com.au: 74.125.82.43 is neither permitted nor denied by SPF record at ntlworld.com) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-proxyuser-ip:date:from:to:cc:subject:message-id:in-reply-to :references:x-mailer:mime-version:content-type :content-transfer-encoding:x-gm-message-state; bh=o804eAFsA9jg3MKzf1uZ1j/4AqTREPbjmt4fiUDiNtc=; b=a1clUJXstMZj34+2CiHHbU8LG6F+++LMyV7JL8i5sc6h/xToIEMQb5w3EZ8kSQhNEd s+7z/pHu2/oYne7A/4JNYTHmwlN7IrF9RCFPJ07FKNiW5aMBvXJMks2WTg4EpGvhx4+W e39hQTlUINBtk2h1bf01QOqM6hIhaqGcq/T3o5+NAwOZBR6tP9Ybtb+fU36V/ka/HDyQ guplJa8YWD4O5PCIJGuPOfkfVnNv0ruaxJjGf7HtJ2K/Q6csfqOrsIHKH9koLbx4P9KV Ho/R0mxp8QKr7wamNYZTi5M1pcFy9G28+OVU0QTFDo3XllSaC+swsqL6KnScz7pvzBKF bV/A== X-ProxyUser-IP: 82.8.55.192 Date: Tue, 20 Nov 2012 21:05:52 +0000 From: Peter Stephenson To: zsh-workers@zsh.org Cc: Han Pingtian Subject: Re: argv subscript range uses too many memory Message-ID: <20121120210552.19eb87a9@pws-pc.ntlworld.com> In-Reply-To: <121120094443.ZM5584@torch.brasslantern.com> References: <20121108084001.GA7594@localhost.localdomain> <20121108100226.575b0788@pwslap01u.europe.root.pri> <20121110105811.GA7136@localhost.localdomain> <121110065709.ZM4781@torch.brasslantern.com> <20121120130457.GD2500@localhost.localdomain> <121120090300.ZM5552@torch.brasslantern.com> <121120094443.ZM5584@torch.brasslantern.com> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.7; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQmbNx7cHi97H+x5IurdhqIflFowGFeRckDyS2+6ZYbh0cO51yOhqNvJuWELfKqaXj17Gx9O On Tue, 20 Nov 2012 09:44:42 -0800 Bart Schaefer wrote: > So what we need is a fast way to estimate how much uncollected garbage > is in the heap -- or, conversely, a fast way to estimate how close we > are to running out of memory -- so that garbage collection can be put > off until it's necessary. > > Or, as I said before, find a scope in which to pushheap/popheap ... Instead of optimising freeheap for the case where the are lots of heaps, could we just increase HEAPSIZE? It's only 16384 (minus a header), which seems pretty small to me. Or could we make it a variable, so the more memory you acquire the larger it is? Then if you need a lot of memory you're not constantly allocating it in small chunks. -- Peter Stephenson Web page now at http://homepage.ntlworld.com/p.w.stephenson/