From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: GC Date: Sat, 25 Jun 2005 16:48:39 +0200 Message-ID: References: <200506182319.j5INJWF08937@raven.dms.auburn.edu> <200506202312.j5KNCct19091@raven.dms.auburn.edu> <200506212058.j5LKw5P23961@raven.dms.auburn.edu> <874qbqh0lm.fsf@jurta.org> <87mzpf3a5v.fsf_-_@jurta.org> <87y88zv3vm.fsf@jurta.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1119707661 27564 80.91.229.2 (25 Jun 2005 13:54:21 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 25 Jun 2005 13:54:21 +0000 (UTC) Cc: miles@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 25 15:54:19 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DmB6K-0004RN-Av for ged-emacs-devel@m.gmane.org; Sat, 25 Jun 2005 15:53:40 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DmBDZ-0001fs-CY for ged-emacs-devel@m.gmane.org; Sat, 25 Jun 2005 10:01:09 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DmBBb-0001Hs-BJ for emacs-devel@gnu.org; Sat, 25 Jun 2005 09:59:09 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DmBBT-0001GI-MN for emacs-devel@gnu.org; Sat, 25 Jun 2005 09:59:02 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DmBBS-0001Dj-Q1 for emacs-devel@gnu.org; Sat, 25 Jun 2005 09:58:58 -0400 Original-Received: from [192.114.186.66] (helo=romy.inter.net.il) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DmB5M-0004gx-Ay; Sat, 25 Jun 2005 09:52:40 -0400 Original-Received: from HOME-C4E4A596F7 (IGLD-80-230-158-88.inter.net.il [80.230.158.88]) by romy.inter.net.il (MOS 3.5.8-GR) with ESMTP id BQJ83669 (AUTH halo1); Sat, 25 Jun 2005 16:48:42 +0300 (IDT) Original-To: emacs-devel@gnu.org In-reply-to: (gaetan.leurent@ens.fr) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:39496 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:39496 > Cc: miles@gnu.org, Eli Zaretskii , Juri Linkov , > emacs-devel@gnu.org > From: gaetan.leurent@ens.fr (=?iso-8859-1?Q?Ga=EBtan?= LEURENT) > Date: Sat, 25 Jun 2005 15:10:49 +0200 > > > Miles Bader wrote on 25 Jun 2005 14:15:19 +0200: > > > Yes I think that would be a good idea. Setting the cons-threshold to > > say 1 or 2% of RAM size would yield roughly the numbers which are > > being recommended (at 1%, you'd get 640K on a 64MB system, and 5MB on > > a 512MB system). > > This is maybe not a good idea for people who runs emacs on a big server > with a lot a memory and a lot of users The threshold will still be customizable. Defaults are for the frequent situations, they aren't supposed to cover all of them. > (my emacs is running on a server > with 8Gb of RAM -- 66 users are currently using it --, but wasting 80Mo > between each GC doesn't seem very smart) The default value of the GC threshold should probably be limited anyway, using a fixed percent on large systems might hit some quota, and even if it doesn't, it's not a good idea to have it grow linearly.