From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: 17837@debbugs.gnu.org
Subject: bug#17837: 24.4.50; Search very slow
Date: Mon, 23 Jun 2014 19:32:21 +0300 [thread overview]
Message-ID: <838uonsi22.fsf@gnu.org> (raw)
In-Reply-To: <83d2dzsk48.fsf@gnu.org>
Here's the profile, with today's trunk. Looks like the function
called by syntax-ppss via funcall is the culprit. The only funcall in
syntax-ppss calls syntax-begin-function, AFAICS.
- command-execute 672 94%
- call-interactively 672 94%
- funcall-interactively 672 94%
- isearch-repeat-forward 663 93%
- isearch-repeat 663 93%
- isearch-update 655 92%
- isearch-lazy-highlight-new-loop 654 92%
- sit-for 654 92%
- redisplay 654 92%
- redisplay_internal (C function) 636 89%
- jit-lock-function 634 89%
- jit-lock-fontify-now 634 89%
- funcall 634 89%
- #<compiled 0x13152f7> 634 89%
- run-hook-with-args 634 89%
- font-lock-fontify-region 634 89%
- font-lock-default-fontify-region 634 89%
- font-lock-fontify-syntactically-region 631 89%
- syntax-propertize 597 84%
- #<compiled 0x106c735> 593 83%
- syntax-ppss 579 81%
- funcall 571 80%
#<compiled 0x106ced3> 569 80%
- syntax-ppss 33 4%
- funcall 33 4%
#<compiled 0x1448019> 33 4%
font-lock-fontify-keywords-region 2 0%
- find-image 2 0%
cond 2 0%
- isearch-search 8 1%
- byte-code 8 1%
- isearch-search-string 8 1%
search-forward-lax-whitespace 8 1%
- isearch-printing-char 7 0%
- isearch-process-search-char 7 0%
- isearch-process-search-string 7 0%
- isearch-search-and-update 7 0%
- isearch-update 7 0%
- isearch-lazy-highlight-new-loop 7 0%
- sit-for 7 0%
- redisplay 7 0%
redisplay_internal (C function) 1 0%
- execute-extended-command 1 0%
- command-execute 1 0%
- call-interactively 1 0%
- funcall-interactively 1 0%
profiler-start 1 0%
- minibuffer-complete 1 0%
- completion-in-region 1 0%
- completion--in-region 1 0%
- #<compiled 0x145b655> 1 0%
- apply 1 0%
- #<compiled 0x4bd08b> 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%
- funcall 1 0%
- #<compiled 0x145b677> 1 0%
- #<compiled 0x145b669> 1 0%
completion-basic-try-completion 1 0%
- ... 36 5%
Automatic GC 36 5%
next prev parent reply other threads:[~2014-06-23 16:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 15:26 bug#17837: 24.4.50; Search very slow Richard Stallman
2014-06-23 15:47 ` Eli Zaretskii
2014-06-23 16:32 ` Eli Zaretskii [this message]
2014-06-23 15:51 ` Stefan Monnier
2014-06-23 16:38 ` Eli Zaretskii
2014-06-23 21:15 ` Stefan Monnier
2014-06-24 1:08 ` Richard Stallman
2014-06-24 2:46 ` Eli Zaretskii
2014-06-24 15:06 ` Stefan Monnier
2014-06-24 15:43 ` Richard Stallman
2014-06-24 15:42 ` Richard Stallman
2014-06-24 15:59 ` Eli Zaretskii
2014-06-24 17:29 ` Stefan Monnier
2014-06-25 11:28 ` Richard Stallman
2014-06-25 11:28 ` Richard Stallman
2014-06-25 13:28 ` Eli Zaretskii
2014-06-26 0:10 ` Richard Stallman
2014-06-26 2:54 ` Stefan Monnier
2014-06-26 18:39 ` Richard Stallman
2014-06-26 14:59 ` Eli Zaretskii
2014-06-26 18:40 ` Richard Stallman
2021-09-19 22:14 ` Stefan Kangas
2021-09-20 6:10 ` Lars Ingebrigtsen
2021-09-20 6:56 ` Stefan Kangas
2021-09-21 22:15 ` Richard Stallman
2021-09-21 22:16 ` Lars Ingebrigtsen
2021-09-20 23:51 ` Richard Stallman
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=838uonsi22.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17837@debbugs.gnu.org \
--cc=rms@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).