unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Kai Ma <justksqsf@gmail.com>
Cc: jb@jeremybryant.net, 71454@debbugs.gnu.org
Subject: bug#71454: 30.0.50; Performance issues with font selection
Date: Mon, 10 Jun 2024 09:31:53 -0700	[thread overview]
Message-ID: <1927ec80-ee2f-1b28-5e43-05f7bd57a21a@gmail.com> (raw)
In-Reply-To: <867cex9fpb.fsf@gnu.org>

On 6/10/2024 4:53 AM, Eli Zaretskii wrote:
> My crystal ball says that the expensive part here is character
> composition.  The above characters belong to scripts that require
> extensive composition rules, take a look at indian.el and its complex
> regexps.

That would show up in a profile, right? Here's what I get when I start 
"emacs -Q", start profiling, and then call "C-h v 
comint-password-prompt-regexp RET". It's not the most interesting 
profile since most of it is probably in C code. I do see 
'auto-compose-chars' in there, however it's got ~0% of the samples from 
the profiler.

I haven't had time to dig into this in any great depth, so this profile 
may of course turn out to be entirely useless...

          910  98% - command-execute
          907  98%  - funcall-interactively
          907  98%   - describe-variable
          907  98%    - help--window-setup
          905  98%     - help-window-setup
            2   0%      - help-window-display-message
            2   0%         auto-compose-chars
            1   0%     - #<compiled 0x14e8696a6b1e2e3f>
            1   0%      - cl-prin1-to-string
            1   0%       - byte-code
            1   0%        - cl-generic-define-method
            1   0%         - cl--generic-make-function
            1   0%          - cl--generic-make-next-function
            1   0%           - cl--generic-get-dispatcher
            1   0%            - byte-compile
            1   0%             - #<subr 
F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_50>
            1   0%                byte-compile-top-level
            1   0%       help-make-xrefs
            3   0%  - byte-code
            2   0%   - read-extended-command
            2   0%    - read-extended-command-1
            2   0%       completing-read-default
            1   0%   - variable-at-point
            1   0%    - find-tag-default
            1   0%       find-tag-default-bounds
           10   1% - ...
            9   0%    Automatic GC
            1   0%  - completion--in-region
            1   0%   - #<compiled -0x68df6976d72fd66>
            1   0%    - apply
            1   0%     - #<compiled -0x1e70b1692b6b395e>
            1   0%      - completion--in-region-1
            1   0%       - completion--do-completion
            1   0%        - completion-try-completion
            1   0%         - completion--nth-completion
            1   0%          - completion--some
            1   0%           - #<compiled 0x3d94d2d3a4c0012>
            1   0%            - completion-basic-try-completion
            1   0%             - completion-boundaries
            1   0%              - help--symbol-completion-table
            1   0%               - help--load-prefixes
            1   0%                - load
            1   0%                   byte-code





  reply	other threads:[~2024-06-10 16:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-09 18:56 bug#71454: 30.0.50; Performance issues with font selection Kai Ma
2024-06-09 22:10 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-09 22:17   ` Kai Ma
2024-06-09 22:34     ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-10  2:14       ` Kai Ma
2024-06-10 12:04         ` Eli Zaretskii
2024-06-09 23:10     ` Jim Porter
2024-06-10  2:18       ` Kai Ma
2024-06-10 11:53         ` Eli Zaretskii
2024-06-10 16:31           ` Jim Porter [this message]
2024-06-10 17:35             ` Eli Zaretskii
2024-06-10 11:55     ` Eli Zaretskii
2024-06-10 12:35       ` Kai Ma
2024-06-10 12:59         ` Eli Zaretskii
2024-06-10 16:42           ` Gerd Möllmann
2024-06-10 17:36             ` Kai Ma
2024-06-10 18:05               ` Gerd Möllmann
2024-06-10 11:58 ` Eli Zaretskii
2024-06-10 12:34   ` Kai Ma
2024-06-10 13:03     ` Eli Zaretskii
     [not found] ` <22612F93-FC37-48E8-8137-E9FF6F5B3A0D@gmail.com>
2024-09-27  6:32   ` Eli Zaretskii
2024-09-27  7:51     ` Kai Ma
2024-09-27 10:29       ` Eli Zaretskii
2024-09-28  3:36     ` Gerd Möllmann
2024-10-12 11:20       ` Eli Zaretskii
2024-10-15 20:34         ` Kai Ma

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=1927ec80-ee2f-1b28-5e43-05f7bd57a21a@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=71454@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jb@jeremybryant.net \
    --cc=justksqsf@gmail.com \
    /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).