Return to BSD News archive
Path: sserve!euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!news.sprintlink.net!howland.reston.ans.net!xlink.net!zib-berlin.de!irz401!uriah.heep!bonnie.heep!not-for-mail
From: j@bonnie.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: How many swap for FreeBSD ??
Date: 2 Aug 1995 11:01:47 +0200
Organization: Private U**x site, Dresden.
Lines: 24
Message-ID: <3vnetr$o7c@bonnie.tcd-dresden.de>
References: <3v84si$8n0@news.ust.hk> <3vjoh5$3gs@blob.best.net> <3vjq9m$h63@cronkite.seas.gwu.edu> <kientzleDCLvGw.D1F@netcom.com>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
<kientzle@netcom.com> wrote:
> One point that has a pretty big effect is which X server you use.
>I've watched my S3 server grow to over 40 megabytes under certain
>situations (Netscape can be _sooo_ antisocial! <sigh>). I understand the
>plain vanilla SVGA server is much more polite.
I don't believe it's the kind of X server you're running. Netscape is
blatant, it pre-allocates a lot of server resources. Unfortunately,
the XFree86(tm) 3.1.1 config files shipped with using the standard
malloc for everything (previous versions have been using gnumalloc,
but there have once been problems reported).
Gnumalloc has the advantage that it can give memory back to the system
(in case a large contiguous region on the top of memory becomes freed
again), while standard malloc doesn't. XFree86 3.1.2 switched back to
the gnumalloc default, and the XFree86 people have also been starting
with experiments for a totally different malloc. This might be a
better solution for future releases.
--
cheers, J"org private: joerg_wunsch@uriah.heep.sax.de
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)