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 KAA13518; Fri, 6 Apr 2001 10:46:50 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id KAA13735 for ; Fri, 6 Apr 2001 10:46:49 +0200 (MET DST) Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by nez-perce.inria.fr (8.11.1/8.10.0) with ESMTP id f368kmf17396 for ; Fri, 6 Apr 2001 10:46:48 +0200 (MET DST) Received: from checkerlap.d6.com ([64.163.212.241]) by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0GBD000CS4DNWW@mta5.snfc21.pbi.net> for caml-list@inria.fr; Fri, 6 Apr 2001 01:46:36 -0700 (PDT) Date: Fri, 06 Apr 2001 01:47:41 -0700 From: Chris Hecker Subject: [Caml-list] toplevel bogging down after a while X-Sender: def6@shell16.ba.best.com To: caml-list@inria.fr Message-id: <4.3.2.7.2.20010406011300.032eed90@shell16.ba.best.com> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Content-type: text/plain; charset="us-ascii" Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk I tend to use this emacs macro a lot while I'm developing: (define-key caml-mode-map "\C-c\C-t" (lambda () "Eval the entire buffer with *inferior-caml*" (interactive) (inferior-caml-eval-region (point-min) (point-max)))) I love having a language with a toplevel, especially when I can run tk/gl apps straight out of emacs! Groovy. However, after about 15 or 20 runs of my 300 line labltk/lablgl app, the runtime performance of the app starts really decreasing. If I kill the inferior-caml process, and start it up again, everything's back to normal. It seems like the gl-drawn mouse cursor is slowing down even more than the app, but the app definitely slows way down. Below are some Gc.stat () calls at various times. Is it likely that this is Gc related? I don't know how to read the stats below and whether they're saying anything. I don't mind restarting the inferior-caml process, but is this some problem with my app that I'm going to run into if the native code version is run for long enough? Is there any way I can figure out what's causing this? Is there a way to reset the toplevel without killing the process? This is on Win98, OCaml 3.00, with a custom toplevel (built with unix, lablgl, and labltk). Chris fresh inferior-caml: {Gc.minor_words=104712; Gc.promoted_words=41874; Gc.major_words=101633; Gc.minor_collections=5; Gc.major_collections=1; Gc.heap_words=126976; Gc.heap_chunks=2; Gc.live_words=101633; Gc.live_blocks=20071; Gc.free_words=25343; Gc.free_blocks=2; Gc.largest_free=25166; Gc.fragments=0; Gc.compactions=0} after one run, things are nice and fast: {Gc.minor_words=4963116; Gc.promoted_words=481604; Gc.major_words=681315; Gc.minor_collections=153; Gc.major_collections=3; Gc.heap_words=717824; Gc.heap_chunks=11; Gc.live_words=272130; Gc.live_blocks=77445; Gc.free_words=50961; Gc.free_blocks=222; Gc.largest_free=45281; Gc.fragments=54; Gc.compactions=0} after ten or so runs, things are chugging at this point: {Gc.minor_words=26965304; Gc.promoted_words=3293457; Gc.major_words=3519501; Gc.minor_collections=824; Gc.major_collections=8; Gc.heap_words=2241536; Gc.heap_chunks=35; Gc.live_words=201410; Gc.live_blocks=63981; Gc.free_words=222291; Gc.free_blocks=2316; Gc.largest_free=34683; Gc.fragments=1258; Gc.compactions=0} ------------------- To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr