From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: Long lines and bidi
Date: Fri, 08 Feb 2013 18:52:06 +0200 [thread overview]
Message-ID: <83y5ey7npl.fsf@gnu.org> (raw)
In-Reply-To: <51152A00.6070101@yandex.ru>
> Date: Fri, 08 Feb 2013 20:38:24 +0400
> From: Dmitry Antipov <dmantipov@yandex.ru>
> CC: emacs-devel@gnu.org
>
> On 02/08/2013 06:46 PM, Eli Zaretskii wrote:
>
> > Btw, if you are serious about finding a solution to the long-line
> > display misfeature (or any other too-slow redisplay situation), I
> > generally find it necessary to do precision timing of the suspicious
> > parts of code, because otherwise it is impossible to find the actual
> > culprits. On GNU/Linux, I use the following simple function:
>
> Ah, please, there is a difference between 2013 and 1980.
Sorry, you lost me here.
> 1) perf record -e stalled-cycles-frontend -e stalled-cycles-backend -F 10000 [workload]
> 2) perf report --stdio ==>
>
> 25.18% emacs emacs [.] scan_buffer
> 7.04% emacs emacs [.] bidi_resolve_weak
That's why testing redisplay on buffers which are predominantly
punctuation will give you unrealistic measurements. (If you want to
understand why, read UAX#9.)
> So, ~90% of time spent in scan_buffer is:
>
> 799 while (*cursor != target && --cursor >= ceiling_addr)
> 800 ;
Which cannot be optimized.
next prev parent reply other threads:[~2013-02-08 16:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877gmp5a04.fsf@ed.ac.uk>
[not found] ` <83vca89izh.fsf@gnu.org>
[not found] ` <5110906D.7020406@yandex.ru>
[not found] ` <83fw1aac3d.fsf@gnu.org>
[not found] ` <51120360.4060104@yandex.ru>
[not found] ` <jwvehgtfrd6.fsf-monnier+emacs@gnu.org>
[not found] ` <51127363.5030203@yandex.ru>
[not found] ` <834nhp9u9j.fsf@gnu.org>
2013-02-08 13:33 ` Long lines and bidi [Was: Re: bug#13623: ...] Dmitry Antipov
2013-02-08 14:07 ` Eli Zaretskii
2013-02-08 14:46 ` Long lines and bidi Eli Zaretskii
2013-02-08 16:38 ` Dmitry Antipov
2013-02-08 16:52 ` Eli Zaretskii [this message]
2013-02-09 3:34 ` Paul Eggert
2013-02-09 8:46 ` Eli Zaretskii
2013-02-09 9:05 ` Paul Eggert
2013-02-09 9:33 ` Eli Zaretskii
2013-02-11 2:33 ` Paul Eggert
2013-02-09 10:01 ` Eli Zaretskii
2013-02-10 16:57 ` Eli Zaretskii
2013-02-11 5:43 ` Dmitry Antipov
2013-02-11 7:54 ` Dmitry Antipov
2013-02-11 16:47 ` Eli Zaretskii
2013-02-11 23:55 ` Paul Eggert
2013-02-11 16:42 ` Eli Zaretskii
2013-02-11 17:53 ` Dmitry Antipov
2013-02-11 18:10 ` Eli Zaretskii
2013-02-11 18:21 ` Dmitry Antipov
2013-02-11 17:17 ` Eli Zaretskii
2013-02-11 17:55 ` Drew Adams
2013-02-11 18:13 ` Eli Zaretskii
2013-02-08 16:21 ` Long lines and bidi [Was: Re: bug#13623: ...] Dmitry Antipov
2013-02-08 17:04 ` Eli Zaretskii
2013-02-08 15:33 ` Stefan Monnier
2013-02-08 16:05 ` Eli Zaretskii
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=83y5ey7npl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmantipov@yandex.ru \
--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).