unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Miroslav Silovic <miro@puremagic.com>
Cc: guile-devel@gnu.org
Subject: Re: GUILE GC -- Write barrier for vectors
Date: Mon, 15 Jul 2002 13:36:37 +0200	[thread overview]
Message-ID: <3D32B3C5.5050204@puremagic.com> (raw)
In-Reply-To: 15666.43843.623166.460512@meddo.cs.uu.nl

Han-Wen Nienhuys wrote:

>I'm quite sure that free/malloc bytes reported are matched. However,
>most counts are a little underestimated. This is impossible to
>prevent, since we are using classes derived from smobbed C++
>baseclasses (You can't get correct object sizes in destructors and
>constructors).
>
>  
>

AFAIK, this shouldn't be the problem (it should only cause your memory 
usage to be
larger than necessary). Did you try to monitor and compare GC 
frequencies on both
machines (and log the bytes allocated etc.) ?

    Miro



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-07-15 11:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-14 22:14 GUILE GC -- Write barrier for vectors hanwen
2002-07-15 10:56 ` Miroslav Silovic
2002-07-15 11:00   ` Han-Wen Nienhuys
2002-07-15 11:36     ` Miroslav Silovic [this message]
2002-07-15 16:49 ` Dirk Herrmann
2002-07-15 18:22   ` Han-Wen Nienhuys
2002-07-15 20:07     ` Dirk Herrmann
2002-07-15 23:02       ` Han-Wen
2002-07-16  9:22         ` Han-Wen Nienhuys
2002-07-16 23:04         ` Dirk Herrmann
2002-07-16 23:26           ` Han-Wen
2002-07-17 21:53           ` Han-Wen
2002-07-19 23:48             ` Dirk Herrmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D32B3C5.5050204@puremagic.com \
    --to=miro@puremagic.com \
    --cc=guile-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).