From: Eli Zaretskii <eliz@gnu.org>
To: zack.stackson@gmail.com
Cc: 15390@debbugs.gnu.org
Subject: bug#15390: 24.3; scrolling in emacs,w32 uses 100% cpu
Date: Mon, 16 Sep 2013 10:13:59 +0300 [thread overview]
Message-ID: <837gehqlvs.fsf@gnu.org> (raw)
In-Reply-To: <838uyxqndb.fsf@gnu.org>
> Date: Mon, 16 Sep 2013 09:41:52 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 15390@debbugs.gnu.org
>
> Emacs 24's display performance is sensitive to the paragraph length as
> well. A paragraph start and end are defined for this purpose as empty
> lines. Is it possible that the text files you used didn't have any
> empty lines at all? If so, can you try files that do have empty
> lines?
In addition, the characters that begin a paragraph might be of
importance. You say "text file", so I presume that is human-readable
text, but it could also be a file with many digits and punctuation
characters -- these make redisplay work harder.
IOW, please show some representative portion(s) of the file(s) in
question, or perhaps even the entire file, if you can share it.
> I can only see performance similar to what you report on a laptop with
> a Core i3-2328M at 2.2 GHz (running Windows 7 64-bit), a much slower
> machine. I will try later on a desktop Windows 7 machine.
Did that, and saw 20% to 30% CPU load, on a system that is powered by
a Core 2 Duo CPU, clearly much slower than yours.
Bottom line: I'm quite sure the file(s) you are using somehow hit the
display engine in its underbelly.
next prev parent reply other threads:[~2013-09-16 7:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-15 18:41 bug#15390: 24.3; scrolling in emacs,w32 uses 100% cpu Zack Stackson
2013-09-16 6:41 ` Eli Zaretskii
2013-09-16 7:13 ` Eli Zaretskii [this message]
2013-09-19 3:53 ` Zack Stackson
2013-09-19 7:51 ` Eli Zaretskii
2013-09-23 5:32 ` Zack Stackson
2013-09-23 7:07 ` Eli Zaretskii
2019-09-26 12:38 ` Stefan Kangas
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=837gehqlvs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15390@debbugs.gnu.org \
--cc=zack.stackson@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.