From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id QAA04256; Sat, 8 Dec 2001 16:41:43 +0100 (MET) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id QAA04412 for ; Sat, 8 Dec 2001 16:41:42 +0100 (MET) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by concorde.inria.fr (8.11.1/8.11.1) with ESMTP id fB8FfeT10286; Sat, 8 Dec 2001 16:41:41 +0100 (MET) Received: (from xleroy@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id QAA04454; Sat, 8 Dec 2001 16:41:40 +0100 (MET) Date: Sat, 8 Dec 2001 16:41:40 +0100 From: Xavier Leroy To: Christophe Raffalli Cc: caml-list@inria.fr Subject: Re: [Caml-list] lablGL an size ... Message-ID: <20011208164140.A4455@pauillac.inria.fr> References: <3C10E3BB.890AA753@ieee.org> <3C113674.87F89565@univ-savoie.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3C113674.87F89565@univ-savoie.fr>; from Christophe.Raffalli@univ-savoie.fr on Fri, Dec 07, 2001 at 10:36:52PM +0100 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk > I had problem understanding why my program took 90Mb ... It doesn't "take" 90 M properly speaking. The 90 M figure is what "ps" reports. > Then I tracked the problem: the "simple" example from the distribution of > lablGL 0.96 take around 80Mb (see below) > and it seems it is the minimum size of any lablGL program ! ... and probably of any program that uses Open GL on your machine. > Is this normal ? May be the video-RAM is included ??? Exactly. The X server, as well as programs that access the hardware 3D acceleration of your video card (and that is presumably the case with Open GL programs) map the video RAM in their own memory space, often two or three times (don't ask me why). With a modern video card, that means a lot of memory space. But it's not memory that your program "takes", properly speaking, just accesses to shared resources. (The same goes, to some extent, for the shared libraries used by your program.) To understand how much memory your program really occupies, it helps to have a close look at /proc//maps. - Xavier "I developed OCaml 1.00 on a PC that had less RAM than your GeForce 2MX video card" Leroy ------------------- Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr