all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Performance problems (CPU 100%) with NULs in files
Date: Sat, 24 Sep 2011 09:04:15 +0300	[thread overview]
Message-ID: <83aa9uqxwg.fsf@gnu.org> (raw)
In-Reply-To: <BC5672F8AD4C054BAF167C9801500D1A510C37D4@USSLMMBX003.net.plm.eds.com>

> From: "Ludwig, Mark" <ludwig.mark@siemens.com>
> Date: Sat, 24 Sep 2011 00:20:24 +0000
> 
> 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.)

Yes, this is a well-known case that causes the current display engine
become very slow.  IIRC, it has been like that since Emacs 21.1.

> 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.

Please file a bug report.  It is not unreasonable to expect the code
to be optimized in some way to cater to such use cases.

And thanks for taking your time to investigate this.



  parent reply	other threads:[~2011-09-24  6:04 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
2011-09-24  6:04     ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83aa9uqxwg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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 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.