From: "Berry, Charles" <ccberry@ucsd.edu>
To: Ken Mankoff <mankoff@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: BUG? WAS: Re: Painfully Slow Export
Date: Thu, 14 Jun 2018 18:34:40 +0000 [thread overview]
Message-ID: <CBAF8544-AF0F-45DC-87DB-748C3C4A6BBC@ucsd.edu> (raw)
In-Reply-To: <CAFdBzErGtxoNipO6WMdEWYaYJLwGTmxTr-6zeHWua2b0zq9wOQ@mail.gmail.com>
tl;dr: `:exports results :noweb no-export :eval never-export' needlessly expands <<noweb>> code causing massive slowdowns on export.
> On Jun 13, 2018, at 9:42 PM, Ken Mankoff <mankoff@gmail.com> wrote:
>
> One more thought - even if your system is significantly faster for some unknown reason - why is export taking ~15 seconds for 200 blocks *when you aren't exporting any of the code*.
> Why is <<noweb>> expansion occurring if ":eval never-export" is set? There seems to be something inefficient going on here.
>
>
Using your ECM, C-c C-v C-i on your `baz' block. Note `:exports code'
,----
| Name: baz
| Lang: sh
| Properties:
| :header-args :eval never-export
| :header-args:sh nil
| Header Arguments:
| :cache no
| :eval never-export
| :exports code
| :hlines no
| :noweb yes
| :results verbatim replace
| :session none
| :tangle no
`----
Setting `:exports none' speeds things up a bit more.
Looking back at your earlier posts, I see that you had `:exports results' for your python block but not in your ECM. i.e. you need these header args:
#+PROPERTY: header-args :eval never-export :exports results :noweb no-export
to show how bad things can be in your ECM.
The `:exports results' will *really* slow things down. And this *may* be considered a bug. Babel isn't quite smart enough to sort out that you want results, but do not need to eval the src block nor check the hash in `org-babel-sha1-hash'.
Making matters a bit more complicated, I'd have thought that this
:noweb (if org-export-current-backend "no" "yes")
would be enough to fix things, but it fails on recursive noweb expansions if you try to execute a src block interactively. And maybe that is a bug, too.
HTH,
Chuck
next prev parent reply other threads:[~2018-06-14 18:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 14:01 Painfully Slow Export Ken Mankoff
2018-06-12 15:09 ` Chris
2018-06-12 19:41 ` Ken Mankoff
2018-06-12 15:51 ` Berry, Charles
2018-06-12 19:41 ` Ken Mankoff
2018-06-12 21:07 ` Berry, Charles
2018-06-12 21:15 ` Ken Mankoff
2018-06-12 21:30 ` Ken Mankoff
2018-06-12 22:07 ` Berry, Charles
2018-06-13 5:32 ` Ken Mankoff
2018-06-13 17:55 ` Berry, Charles
2018-06-13 18:32 ` Ken Mankoff
2018-06-14 4:42 ` Ken Mankoff
2018-06-14 18:34 ` Berry, Charles [this message]
2018-06-23 21:06 ` BUG? WAS: " Nicolas Goaziou
2018-06-24 1:53 ` Berry, Charles
2018-06-25 13:55 ` Ken Mankoff
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=CBAF8544-AF0F-45DC-87DB-748C3C4A6BBC@ucsd.edu \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@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).