From: Dmitry Gutov <dgutov@yandex.ru>
To: Aaron Jensen <aaronjensen@gmail.com>, 24048@debbugs.gnu.org
Subject: bug#24048: 25.0.95; syntax-ppss can be slow
Date: Mon, 25 Jul 2016 15:42:22 +0300 [thread overview]
Message-ID: <d001029a-32a6-a915-bc83-3c6701f415ac@yandex.ru> (raw)
In-Reply-To: <CAHyO48ywOJY8F7=bJbEPA9mcN1WnZx56fQzbzkFdWZLuACx9MQ@mail.gmail.com>
On 07/25/2016 10:12 AM, Aaron Jensen wrote:
> Sure, just use elixir-mode and this
> file https://gist.githubusercontent.com/aaronjensen/d4cd40347a916dd36c8239afecf64a7d/raw/b52440bb51b96193a365a7f4cc1c8733ba98476f/syntax-ppss-slow-repro.ex
>
> Then do: (benchmark 100 '(syntax-ppss)) at the top of the file and
> compare it to doing it within the `chunk_by` function at the bottom of
> the file. For me it’s 0.2ms at the top and 5.6ms at the bottom.
> Smartparens can do 50-100 syntax-ppss calls for every
> self-insert-command, and 5.6ms is significant latency to add on to every
> keypress.
Is 5.6ms really significant? You should be typing like 200 characters
per _second_ to really notice the difference.
Even 12ms that I'm getting at the bottom of your example file doesn't
sound like it should have effect on the perceptible latency.
next prev parent reply other threads:[~2016-07-25 12:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 14:29 bug#24048: 25.0.95; syntax-ppss can be slow Aaron Jensen
2016-07-25 1:16 ` Dmitry Gutov
2016-07-25 7:12 ` Aaron Jensen
2016-07-25 12:42 ` Dmitry Gutov [this message]
2016-07-25 15:08 ` Aaron Jensen
2018-03-30 13:09 ` Aaron Jensen
2021-12-01 19:47 ` Lars Ingebrigtsen
2021-12-03 2:38 ` Aaron Jensen
2021-12-03 16:26 ` Lars Ingebrigtsen
2021-12-03 17:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-04 1:31 ` Aaron Jensen
2021-12-04 2:41 ` Lars Ingebrigtsen
2021-12-04 14:40 ` Dmitry Gutov
2021-12-04 16:27 ` Aaron Jensen
2021-12-05 0:13 ` Dmitry Gutov
2021-12-05 5:06 ` Aaron Jensen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d001029a-32a6-a915-bc83-3c6701f415ac@yandex.ru \
--to=dgutov@yandex.ru \
--cc=24048@debbugs.gnu.org \
--cc=aaronjensen@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.