From: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16830@debbugs.gnu.org
Subject: bug#16830: [Bug] 24.3.50; massive slow down in forward-line
Date: Sat, 22 Feb 2014 13:27:47 +0100 [thread overview]
Message-ID: <20140222122747.GH27381@pille.home> (raw)
In-Reply-To: <831tyv4c7n.fsf@gnu.org>
Mail von Eli Zaretskii, Sat, 22 Feb 2014 at 13:29:48 +0200:
Hello,
> Doesn't sound like a good idea to me: that would disable the caching
> for much more than this Org file, or even just Org files, right? I
> would suggest to selectively disable caching only for those files that
Ok.
> > I tested it that way with my original file.
> > (elp-instrument-package org; elp-result for org-ctrl-c-ctrl-c)
> >
> > emacs 24.3.50.1 2.083 sec (cache-long-scans nil, set by file-find-hook)
> > emacs 24.3.1 0.758 sec (cache-long-line-scan nil; as it was)
> >
> > So it is better, but not so good as in the old emacs.
>
> I see no difference in the code that could justify this, and on my
> system "C-c C-c" in both versions completes in the same time after
> disabling the caching, certainly much faster than 2 sec. So I don't
> see how such a 2.5 factor could be explained, except perhaps by some
> additional local customizations on your system (I tested in "emacs -Q").
Argh... you're right, here the measurement with "emacs -Q":
(elp-instrument-package org; elp-result for org-ctrl-c-ctrl-c)
my original org-mode file:
emacs 24.3.50.1 2.065 sec (cache-long-scans nil, set local)
emacs 24.3.1 0.722 sec (cache-long-line-scan nil; as it was)
test-neuter.org:
emacs 24.3.50.1 0.925 sec (cache-long-scans nil, set local)
emacs 24.3.1 0.381 sec (cache-long-line-scan nil; as it was)
With kind regards,
Stefan
--
Stefan-W. Hahn It is easy to make things.
It is hard to make things simple.
next prev parent reply other threads:[~2014-02-22 12:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 12:16 bug#16830: [Bug] 24.3.50; massive slow down in forward-line Stefan-W. Hahn
2014-02-21 12:32 ` Eli Zaretskii
2014-02-21 15:51 ` Stefan-W. Hahn
2014-02-21 17:50 ` Stefan Monnier
2014-02-22 8:38 ` Stefan-W. Hahn
[not found] ` <20140222083926.GC27381@pille.home>
2014-02-22 9:18 ` Eli Zaretskii
2014-02-22 11:08 ` Stefan-W. Hahn
2014-02-22 11:29 ` Eli Zaretskii
2014-02-22 11:36 ` Eli Zaretskii
2014-02-22 12:33 ` Stefan-W. Hahn
2014-02-22 12:55 ` Juanma Barranquero
2014-02-22 15:06 ` Stefan-W. Hahn
2014-02-22 13:05 ` Eli Zaretskii
2014-02-21 7:43 ` Stefan-W. Hahn
2014-02-23 18:04 ` Eli Zaretskii
2014-02-22 12:27 ` Stefan-W. Hahn [this message]
2014-03-10 18:58 ` Eli Zaretskii
2014-03-11 8:08 ` martin rudalics
2014-03-11 17:03 ` Eli Zaretskii
2014-03-12 14:12 ` Stefan Monnier
2014-03-16 16:32 ` Eli Zaretskii
2014-03-17 15:05 ` bug#16830: " Dmitry Antipov
2014-03-17 16:39 ` Eli Zaretskii
2014-06-22 16:50 ` Eli Zaretskii
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=20140222122747.GH27381@pille.home \
--to=stefan.hahn@s-hahn.de \
--cc=16830@debbugs.gnu.org \
--cc=eliz@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).