unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: ediff-next-difference very slow
Date: Wed, 17 Apr 2002 17:56:39 +0300	[thread overview]
Message-ID: <4532-Wed17Apr2002175638+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <15549.30433.173962.449867@tfkp00.physik.uni-erlangen.de> (message from Roland Winkler on Wed, 17 Apr 2002 15:21:37 +0200)

> From: Roland Winkler <roland.winkler@physik.uni-erlangen.de>
> Date: Wed, 17 Apr 2002 15:21:37 +0200
> 
> According to my-ediff-next, ediff-next-difference requires 1 or 2
> seconds in a fresh emacs session on my old pentium processor. But an
> emacs session that has been running for many days requires 6 or
> 7 seconds for each of the two differences between the files foo
> and bar.
> 
> What's going on here? Is this a known problem? How can I try to
> further pin down why ediff becomes so slow?

It seems that having many overlays in a buffer slows down Emacs quite
a bit.  Perhaps this problem is another manifestation of that?

> PS: node `Compilation Tips' in the elisp manual says
> 
>    * Profile your program with the `profile' library or the `elp'
>      library.  See the files `profile.el' and `elp.el' for instructions.
> 
> However, in profile.el it says that profile.el has become obsolete.

Thanks, I fixed this for the next release.

  reply	other threads:[~2002-04-17 14:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17 13:21 ediff-next-difference very slow Roland Winkler
2002-04-17 14:56 ` Eli Zaretskii [this message]
2002-04-17 15:14   ` Roland Winkler
2002-04-17 17:11     ` Eli Zaretskii
2002-04-18 18:44     ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2002-04-19 21:31 Michael Kifer
2002-04-20 12:02 ` Roland Winkler
2002-04-22  8:46 ` Ralf Fassel

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=4532-Wed17Apr2002175638+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=bug-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 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).