unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Dan Nicolaescu <dann@ics.uci.edu>, 4222@emacsbugs.donarmstrong.com
Cc: cyd@stupidchicken.com, 4222@emacsbugs.donarmstrong.com
Subject: bug#4222: calls to char_table_ref slow down 23.1 (vs 22.3)
Date: Sat, 19 Sep 2009 14:37:28 +0900	[thread overview]
Message-ID: <tl7tyyzlckn.fsf@m17n.org> (raw)
In-Reply-To: <200909190443.n8J4hBNM011012@godzilla.ics.uci.edu> (message from Dan Nicolaescu on Fri, 18 Sep 2009 21:43:11 -0700 (PDT))

In article <200909190443.n8J4hBNM011012@godzilla.ics.uci.edu>, Dan Nicolaescu <dann@ics.uci.edu> writes:

> I can't reproduce this problem now.  Following your recipe, I do observe
> the indentation taking a looong time, but char_table_ref is not called.
> Presumably, Handa-san's 2009-08-25 and 2009-08-27 changes fixed this.
> Should I close the bug, or is there still a problem?

> There still is a problem, but it is not caused by char_table_ref, that
> part was fixed by Handa-san.
> It's up to you if you want to keep this bug, just retitle it, or close it.

We still have a problem of slow GC caused by many elements
of char-tables (mostly because of charset encoders).  My
idea for fixing it is to somehow distinguish a char-table
that has only integer or (interned) symbol elements from the
other normal char-tables, and optimize mark_char_table for
it.  But, at the moment, I don't have a time to work on it.

Perhaps we should open a new bug for that.

---
Kenichi Handa
handa@m17n.org







  reply	other threads:[~2009-09-19  5:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18 23:30 bug#4222: calls to char_table_ref slow down 23.1 (vs 22.3) Chong Yidong
2009-09-19  4:43 ` Dan Nicolaescu
2009-09-19  5:37   ` Kenichi Handa [this message]
2009-09-24  4:05     ` Kenichi Handa
  -- strict thread matches above, loose matches on Subject: below --
2009-08-21  5:18 Dan Nicolaescu
2009-08-21  6:34 ` Kenichi Handa
2009-08-21  7:08   ` Dan Nicolaescu

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=tl7tyyzlckn.fsf@m17n.org \
    --to=handa@m17n.org \
    --cc=4222@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    --cc=dann@ics.uci.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.
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).