From: Le Wang <l26wang@gmail.com>
To: "Ludwig, Mark" <ludwig.mark@siemens.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Performance problems (CPU 100%) with NULs in files
Date: Sat, 24 Sep 2011 08:50:12 +0800 [thread overview]
Message-ID: <CAM=K+iqNh5q+t9wNgaykbio_GNpTOQjw8yjGR7ptDee0XkyfEg@mail.gmail.com> (raw)
In-Reply-To: <BC5672F8AD4C054BAF167C9801500D1A510C37D4@USSLMMBX003.net.plm.eds.com>
[-- Attachment #1: Type: text/plain, Size: 2600 bytes --]
File a bug. Let the powers that be decide whether is fix worthy or not.
This way even if it's closed as wont fix, at least when someone does a bug
search in the future they'll see that a similar issue has come up.
On Sat, Sep 24, 2011 at 8:20 AM, Ludwig, Mark <ludwig.mark@siemens.com>wrote:
> > From: Eli Zaretskii
> > Subject: Re: Performance problems (CPU 100%) with NULs in files
> >
> > > From: "Ludwig, Mark" <ludwig.mark@siemens.com>
> > > Thread-Topic: Performance problems (CPU 100%) with NULs in files
> > > Date: Wed, 21 Sep 2011 21:08:42 +0000
> > >
> > > What happens is that as I scroll through the file, when the NULs are
> > visible, Emacs gets into some intensive processing for a long time
> > (minutes, sometimes!). It eventually unwinds and repaints the display,
> > but any movement of point sends it into this loop again. I have found
> > that M-< or M-> will quickly reposition away from the problem (assuming
> > the beginning and/or end of the file do not contain NULs). Most other
> > movement operations send it into the loop.
> >
> > Does it help to visit such files without code conversions, i.e.
> >
> > M-x find-file-literally RET FILENAME RET
> >
> > ?
> >
> > If not, please file a bug report and attach to it an example file that
> > causes this slowdown.
>
> Thanks for the advice, but I have investigated and decided this is probably
> too unusual to expect any "fix" for it.
>
> What I have found is that the "problem" is due to a "line" of text being
> extremely long. In the test file I have, it is ~800,000 characters (bytes).
> (It came to me with NULs, but I can replace those with any other printable
> character and get the same result.)
>
> What I find is that some movement actions are rather slow -- take 4-7
> seconds -- while others are extremely quick. Specifically, the "forward"
> movement actions (C-e, M-f) are slow, while the "backward" movement actions
> (C-a, M-b) are instantaneous. Reposition (C-l) is also slow, as are the
> line-oriented commands (C-p, C-n).
>
> Thinking through the magnitude of the oddity, I don't think it would be
> reasonable to expect Emacs to handle this any better than it does. It's
> just gratifying that C-g works, so I can interrupt it when I stumble into
> some junk, and now that I know which actions are fast and slow, I can work
> around it.
>
> OTOH, if you guys really think this is worth asking any developer to fix,
> I'll file a bug report. I don't need to send any data, because it's easy to
> reproduce this behavior starting with an empty buffer.
>
> Thanks!
>
> Mark
>
>
>
--
Le
[-- Attachment #2: Type: text/html, Size: 3276 bytes --]
next prev parent reply other threads:[~2011-09-24 0:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 21:08 Performance problems (CPU 100%) with NULs in files Ludwig, Mark
2011-09-22 4:30 ` Drew Adams
2011-09-22 13:00 ` Ludwig, Mark
2011-09-22 5:44 ` Eli Zaretskii
2011-09-22 12:58 ` Ludwig, Mark
2011-09-24 0:20 ` Ludwig, Mark
2011-09-24 0:50 ` Le Wang [this message]
2011-09-24 6:04 ` Eli Zaretskii
2011-09-24 13:32 ` Ludwig, Mark
2011-09-24 14:15 ` Eli Zaretskii
2011-09-22 6:09 ` XeCycle
2011-09-22 12:58 ` Ludwig, Mark
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='CAM=K+iqNh5q+t9wNgaykbio_GNpTOQjw8yjGR7ptDee0XkyfEg@mail.gmail.com' \
--to=l26wang@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=ludwig.mark@siemens.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.
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).