unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, 17837@debbugs.gnu.org
Subject: bug#17837: 24.4.50; Search very slow
Date: Tue, 24 Jun 2014 11:06:10 -0400	[thread overview]
Message-ID: <jwvsimucuvi.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <834mzbrplv.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 24 Jun 2014 05:46:52 +0300")

>> I counted around 45 seconds before it found the second occurrence.

Richard, was that in an "emacs -Q"?

> For me, the first one is slower: about 5 to 6 sec.  The second
> occurrence takes maybe 3.  Stefan, what's your timing?

Again trying it on my AMD E-350 machine, using the emacs-24 branch built
with -Og and enable-checking (on Debian testing), I get about half of
your times (about 2-3s for the first search and barely more than 1s for
the second).

Opening the file and doing M-> took 6s.
`emacs23' (Debian's build, i.e. probably with -O2 and without
enable-checking) took 4s for the M-> test.

On my fit-pc2 (Intel Atom, 1G RAM), the emacs-24 branch took 8s to do
the M->.
And on my Mele A2000 (i.e. Allwinner 1GHz A10 CPU with 512M of RAM), it
took 18s.

> Anyway, you may wish to experiment with setting jit-lock-defer-time to
> a non-nil value.  E.g., try setting it to 0.25 or 0.5 sec, and see if
> that gives good results.

I think we should first try and figure out why his second search takes
45s instead of a couple seconds (I expect his Longsoon might be slower
than my Atom, but not significantly slower than my little ARM machine).


        Stefan





  reply	other threads:[~2014-06-24 15:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23 15:26 bug#17837: 24.4.50; Search very slow Richard Stallman
2014-06-23 15:47 ` Eli Zaretskii
2014-06-23 16:32   ` Eli Zaretskii
2014-06-23 15:51 ` Stefan Monnier
2014-06-23 16:38   ` Eli Zaretskii
2014-06-23 21:15     ` Stefan Monnier
2014-06-24  1:08     ` Richard Stallman
2014-06-24  2:46       ` Eli Zaretskii
2014-06-24 15:06         ` Stefan Monnier [this message]
2014-06-24 15:43           ` Richard Stallman
2014-06-24 15:42         ` Richard Stallman
2014-06-24 15:59           ` Eli Zaretskii
2014-06-24 17:29             ` Stefan Monnier
2014-06-25 11:28             ` Richard Stallman
2014-06-25 11:28             ` Richard Stallman
2014-06-25 13:28               ` Eli Zaretskii
2014-06-26  0:10                 ` Richard Stallman
2014-06-26  2:54                   ` Stefan Monnier
2014-06-26 18:39                     ` Richard Stallman
2014-06-26 14:59                   ` Eli Zaretskii
2014-06-26 18:40                     ` Richard Stallman
2021-09-19 22:14 ` Stefan Kangas
2021-09-20  6:10   ` Lars Ingebrigtsen
2021-09-20  6:56     ` Stefan Kangas
2021-09-21 22:15     ` Richard Stallman
2021-09-21 22:16       ` Lars Ingebrigtsen
2021-09-20 23:51   ` Richard Stallman

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=jwvsimucuvi.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=17837@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rms@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).