all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: sand@blarg.net
To: emacs-devel@gnu.org
Subject: Performance regression in CVS HEAD's *compilation* buffer
Date: Tue, 3 Feb 2009 19:42:39 -0800	[thread overview]
Message-ID: <18825.3759.960897.974404@priss.frightenedpiglet.com> (raw)

I updated my CVS tree to HEAD today (2009-02-03, around noon PST),
compiled it, and started using it.  My previous sync had been around
2008-12-01.  During that interval, the performance of inserting long
lines into the *compilation* buffer has dropped by an order of
magnitude.

Here's a simple test case to reproduce:

* In *scratch*, create 96 lines of "x" characters, 64 characters wide.

  <f3> C-u 64 C-u x C-m <f4>
  C-u 95 <f4>

* Put them all onto a single line.

  M-<
  C-u 10000 C-x f
  M-q

* Put an "echo" on the front to make it an invokable command, and copy
  it to a register.

  e c h o <SPC>
  C-x h
  C-x r x c

* Run `compile' with that command:

  M-x compile
  C-a C-k
  C-x r i c
  <RET>

It used to take on the order of 10 seconds to complete.  For example,
on my home machine:

  -*- mode: compilation; default-directory: "~/" -*-
  Compilation started at Tue Feb  3 19:28:40

  echo [...]

  [...]

  Compilation finished at Tue Feb  3 19:28:50

(Output elided.)  With CVS HEAD, this takes well over a minute.  In
both cases, Emacs is completely unresponsive during this display
period.  This is a big problem when running Make with extremely long
(~6kB) output lines.

My home machine is a Debian box running a snapshot of CVS HEAD from
2009-01-11, and I'm unable to reproduce it here, so the performance
drop seems to happened sometime between the 11th and today.

Thanks,

Derek




             reply	other threads:[~2009-02-04  3:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-04  3:42 sand [this message]
2011-01-29  5:28 ` Performance regression in CVS HEAD's *compilation* buffer Stefan Monnier
2011-01-29  6:24   ` David Kastrup
2011-01-29 15:46     ` Stefan Monnier

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=18825.3759.960897.974404@priss.frightenedpiglet.com \
    --to=sand@blarg.net \
    --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 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.