From: Daniel Bausch <bausch@dvs.tu-darmstadt.de>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: another example of org being slow, with some analysis
Date: Fri, 19 Jun 2015 08:19:14 +0200 [thread overview]
Message-ID: <877fr0w78d.fsf@gelnhausen.dvs.informatik.tu-darmstadt.de> (raw)
In-Reply-To: <87vbekc1iy.fsf@alphaville.usersys.redhat.com> (Nick Dokos's message of "Thu, 18 Jun 2015 14:30:29 -0400")
Hi!
Nick Dokos <ndokos@gmail.com> writes:
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>
>> The output of the ELP profiler is here:
>>
>> ...
>> org-goto-line 104 10.761145733 0.1034725551
>> ..
>> org-current-line 66 6.8422078910 0.1036698165
>> ...
>
> I find these two difficult to explain: they account for the vast
> majority of the time, they don't call anything other than basic emacs
> lisp functions (which should be very fast) and they take an unbelievably
> long 0.1 s/call - I did a profile of a single call of each in a file
> where wc reports these stats:
>
> 12961 270362 4317977 /home/nick/lib/notes/notes.org
>
> and I got 0.002s for the first (going to line 6000, about the middle of
> the file) and 0.0004s for the second: a factor of 50 smaller for the
> first and a factor of 250 smaller for the second.
>
> Maybe it's an artifact of profiling, but maybe you can try instrumenting
> these two functions and doing something similar. Do you still get 0.1s
> for each call?
Line 6000 is indeed quite "lame". I have similar problems like Eric. A
table recalculation at line 43868 takes about a minute at my quite fast
machine. I also tracked that down to org-current-line. One interesting
detail is that this depends on the buffer encoding. With ASCII the
recalculation takes less than a second, with utf-8 about a minute.
I think it actually is not an org-mode problem but depends on how
(count-lines 1 (point)) works, as it is using regex searches for the
line endings. I can imagine that the regex parser for utf-8 can be
inefficient.
Regards,
Daniel
--
MSc. Daniel Bausch
Research Assistant (Computer Science)
Technische Universität Darmstadt
http://www.dvs.tu-darmstadt.de/staff/dbausch
next prev parent reply other threads:[~2015-06-19 6:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 16:28 another example of org being slow, with some analysis Eric S Fraga
2015-06-18 18:30 ` Nick Dokos
2015-06-19 6:19 ` Daniel Bausch [this message]
2015-06-19 6:34 ` Daniel Bausch
2015-06-19 7:37 ` Nicolas Goaziou
2015-06-19 7:51 ` Eric S Fraga
2015-06-19 8:28 ` Daniel Bausch
2015-06-19 9:43 ` Eric S Fraga
2015-06-22 6:48 ` Daniel Bausch
2015-06-23 11:16 ` Eric S Fraga
2015-06-19 13:53 ` Nick Dokos
2015-06-19 14:19 ` Eric S Fraga
2015-06-22 7:07 ` Jacob Nielsen
2015-06-18 19:54 ` Ivan Andrus
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877fr0w78d.fsf@gelnhausen.dvs.informatik.tu-darmstadt.de \
--to=bausch@dvs.tu-darmstadt.de \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).