unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Stefan Monnier <foo@acm.com>" <monnier+gnu.emacs.help/news/@flint.cs.yale.edu>
Subject: Re: About performance, hash-tables and garbage collection
Date: 20 Sep 2002 17:07:38 -0400	[thread overview]
Message-ID: <5lfzw4nzdx.fsf@rum.cs.yale.edu> (raw)
In-Reply-To: m33cs4r3oh.fsf@ID-87814.user.dfncis.de

> 1. I have read that hash-tables have a little overhead and that
>    association lists are a little bit faster, when they contain not
>    more than about a dozen of key-value pairs. It is _possible_ that I
>    have to maintain several hundreds or thousand of key/value pairs,
>    but in most cases it will be only a dozen or so. So my question is:
>    how much overhead has a hashtable? Makes it sense to add a
>    condition, like this:
>    (if (> ncolours 15)
>        (gethash colour colour-map)
>      (cdr (assoc (colour colour-map))))

The `if' overhead will probably dwarf the difference, so I'd say,
just use the hash-table.  Most likely any performance problem you'll have
won't come from that anyway.

> 2. I noticed that the garbage collector hits in a little bit too often,

What's too often ?  Why do you care ?
Does it use a significant percentage of the running time ?
If yes, look for things like `append' and things like that to see where
you do most allocation.

>    though I do not know why. I have a lot of `setq'-statements
>    like `(setq pointer (1+ pointer))'. Is it possible that they are
>    the cause?

If the code is interpreted, maybe, tho I don't think so.

>  If so, what could I do?

If you've byte-compiled your code, then an increment (as shown above) will
not allocate any memory and will thus have no influence on GC.


        Stefan

  reply	other threads:[~2002-09-20 21:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20 17:06 About performance, hash-tables and garbage collection Oliver Scholz
2002-09-20 21:07 ` Stefan Monnier <foo@acm.com> [this message]
2002-09-20 23:09   ` Oliver Scholz

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/emacs/

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

  git send-email \
    --in-reply-to=5lfzw4nzdx.fsf@rum.cs.yale.edu \
    --to=monnier+gnu.emacs.help/news/@flint.cs.yale.edu \
    /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).