From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 15841@debbugs.gnu.org, nbtrap@nbtrap.com
Subject: bug#15841: Display bugs with cache-long-lines non-nil
Date: Mon, 11 Nov 2013 04:39:56 +0100 [thread overview]
Message-ID: <87li0vppwz.fsf@web.de> (raw)
In-Reply-To: <83y54w2jo1.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 10 Nov 2013 20:31:10 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> > Anyway, I'll tell you when I have a recipe.
Some elaborations, feel free to ignore.
The culprit was my own code: it placed myriads of invisible overlays
with no properties into the buffer. Under these extreme circumstances,
`line-number-at-pos' indeed gets extremely slow at the end of my 10000
lines buffer: one invocation needs over a second. I saw that with elp
as well as with profiler. Setting `cache-long-scans' to nil (or
removing the overlays) cures this.
Although this is a corner case, I wonder why overlays slow down
`line-number-at-pos' so much for `cache-long-scans' non-nil - is that
expected? Or can the profiler times I saw span redisplay times?
Because, when I use this:
(defmacro my-measure-time (expr)
"Eval EXPR, display how much time it took."
(with-gensyms (time)
`(let ((,time (current-time)))
,expr
(message "%s secs"
(float-time (time-subtract (current-time) ,time))))))
and evaluate (my-measure-time (line-number-at-pos)) manually with M-:
(in the same situation), it shows a very tiny value. But I'm sure that
from code, `line-number-at-pos' really lasts over a second. Strange, I
don't understand it.
Regards,
Michael.
next prev parent reply other threads:[~2013-11-11 3:39 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 21:35 bug#15797: 24.3.50; Info: Mention cache-long-scans Jambunathan K
2013-11-04 0:36 ` Glenn Morris
2013-11-04 4:41 ` Jambunathan K
2013-11-04 13:10 ` Michael Heerdegen
2013-11-04 14:21 ` Jambunathan K
2013-11-05 16:32 ` Eli Zaretskii
2013-11-05 19:24 ` Stefan Monnier
2013-11-06 4:44 ` Jambunathan K
2013-11-08 10:29 ` Eli Zaretskii
2013-11-08 13:13 ` Jambunathan K
2013-11-08 14:02 ` Stefan Monnier
2013-11-08 14:08 ` Jambunathan K
2013-11-08 14:15 ` Eli Zaretskii
2013-11-08 14:33 ` Jambunathan K
2013-11-08 15:16 ` Eli Zaretskii
2013-11-08 10:28 ` Eli Zaretskii
2013-11-08 19:07 ` Nathan Trapuzzano
2013-11-08 20:57 ` Stefan Monnier
2013-11-08 21:36 ` Nathan Trapuzzano
2013-11-08 23:11 ` Nathan Trapuzzano
2013-11-09 8:33 ` Eli Zaretskii
2013-11-08 21:18 ` Eli Zaretskii
2013-11-08 21:22 ` Glenn Morris
2013-11-09 2:37 ` Michael Heerdegen
2013-11-09 8:18 ` bug#15841: Display bugs with cache-long-lines non-nil Eli Zaretskii
2013-11-09 8:31 ` Eli Zaretskii
2013-11-09 8:52 ` Eli Zaretskii
2013-11-09 11:18 ` Eli Zaretskii
2013-11-09 14:02 ` Eli Zaretskii
2013-11-09 21:27 ` Eli Zaretskii
2013-11-10 18:20 ` Michael Heerdegen
2013-11-10 18:31 ` Eli Zaretskii
2013-11-11 3:39 ` Michael Heerdegen [this message]
2013-11-11 16:23 ` Eli Zaretskii
2013-11-13 23:45 ` Michael Heerdegen
2013-11-14 3:51 ` Eli Zaretskii
2013-11-09 8:51 ` Eli Zaretskii
2013-11-11 14:12 ` Stephen Berman
2013-11-11 20:13 ` Eli Zaretskii
2013-11-11 20:38 ` Stephen Berman
2013-11-12 0:38 ` Stephen Berman
2013-11-12 10:03 ` Stephen Berman
2013-11-12 16:31 ` Eli Zaretskii
2013-11-12 21:34 ` Stephen Berman
2013-11-15 16:34 ` Eli Zaretskii
2013-11-15 18:05 ` Stephen Berman
2013-11-16 18:53 ` Andy Moreton
2013-11-16 19:02 ` Eli Zaretskii
2013-11-18 16:32 ` Eli Zaretskii
2013-11-06 18:02 ` bug#15797: 24.3.50; Info: Mention cache-long-scans Michael Heerdegen
2013-11-06 18:17 ` Eli Zaretskii
2013-11-06 18:50 ` Michael Heerdegen
2013-11-06 20:46 ` Eli Zaretskii
[not found] ` <<87wqkltnmk.fsf@web.de>
[not found] ` <<8338n975tf.fsf@gnu.org>
2013-11-06 18:58 ` Drew Adams
2013-11-06 20:56 ` Eli Zaretskii
[not found] ` <handler.15797.D15797.138352538323812.notifdone@debbugs.gnu.org>
2013-11-04 6:27 ` bug#15797: closed (Re: bug#15797: 24.3.50; Info: Mention cache-long-scans) Jambunathan K
[not found] <"<9jiow9uhoa.fsf"@fencepost.gnu.org>
[not found] <<871u2xf9st.fsf@gmail.com>
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=87li0vppwz.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=15841@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=nbtrap@nbtrap.com \
/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.