From: Tom Tromey <tromey@redhat.com>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: indirect threading for bytecode interpreter
Date: Sun, 20 Sep 2009 21:17:10 -0600 [thread overview]
Message-ID: <m3tyyx3s21.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200909210158.n8L1wr55000349@godzilla.ics.uci.edu> (Dan Nicolaescu's message of "Sun, 20 Sep 2009 18:58:53 -0700 (PDT)")
>>>>> "Dan" == Dan Nicolaescu <dann@ics.uci.edu> writes:
Dan> Making the GC generational might help. The first GC after startup does
Dan> 200K mark_object calls, so if most of those don't need to be scanned for
Dan> each GC, then that might help.
Yeah.
Whatever happened to the Boehm GC branch? That seems like the simplest
way to implement this feature.
Dan> If you have a testcase that shows GC problems, maybe posting the test
Dan> case would enticemore people look into it...
Here's a script I've been running on the GDB sources:
http://sourceware.org/ml/gdb-patches/2009-08/msg00390.html
I've profiled (using oprofile) Emacs running this a few times; typical
results show mark_object at 10-12% of runtime. It is probably pretty
easy to reproduce this with a variety of elisp programs.
Tom
next prev parent reply other threads:[~2009-09-21 3:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 16:46 indirect threading for bytecode interpreter Tom Tromey
2009-09-17 18:21 ` Stefan Monnier
2009-09-17 19:20 ` Helmut Eller
2009-09-17 19:38 ` Tom Tromey
2009-09-17 20:41 ` Helmut Eller
2009-09-17 21:06 ` Tom Tromey
2009-09-17 22:48 ` Helmut Eller
2009-09-18 0:59 ` Stefan Monnier
2009-09-18 2:59 ` Tom Tromey
2009-09-17 20:43 ` Stefan Monnier
2009-09-17 20:57 ` Tom Tromey
2009-09-18 19:15 ` Dan Nicolaescu
2009-09-18 20:26 ` Tom Tromey
2009-09-21 1:58 ` Dan Nicolaescu
2009-09-21 3:17 ` Tom Tromey [this message]
2009-09-21 13:13 ` Stefan Monnier
2009-09-21 13:21 ` David Kastrup
2009-09-21 13:47 ` joakim
2009-09-21 14:46 ` Stefan Monnier
2009-09-21 14:27 ` Tom Tromey
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=m3tyyx3s21.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dann@ics.uci.edu \
--cc=emacs-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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).