From: Lawrence Mitchell <wence@gmx.li>
To: emacs-orgmode@gnu.org
Subject: Re: Exporting large documents
Date: Mon, 06 May 2013 17:15:07 +0100 [thread overview]
Message-ID: <878v3sxeyc.fsf@gmx.li> (raw)
In-Reply-To: 51878F09.1050904@ed.ac.uk
Lawrence Mitchell wrote:
[...]
And here's the profile for exporting the whole of orgmanual.org
to latex. You can see that a lot of the time comes from quite
"cheap" functions that are called lots.
org-latex-export-as-latex 1 415.52740777 415.52740777
org-export-to-buffer 1 414.89446185 414.89446185
org-export-as 1 414.89314727 414.89314727
org-entry-get 362909 377.15499961 0.0010392550
org-export-execute-babel-code 1 248.09360062 248.09360062
org-babel-exp-process-buffer 1 248.08328800 248.08328800
org-babel-exp-src-block 137 243.10403972 1.7744820417
org-export-data 33704 241.13159257 0.0071543909
org-babel-get-src-block-info 3811 241.06197704 0.0632542579
org-babel-parse-src-block-match 3811 239.00537768 0.0627146097
org-babel-exp-do-export 137 238.11539604 1.7380685842
org-babel-exp-code 137 237.68002300 1.7348906788
org-babel-expand-noweb-references 24 237.62374387 9.9009893283
org-babel-params-from-properties 3811 237.29706205 0.0622663505
org-entry-get-with-inheritance 99086 234.87738424 0.0023704396
org-get-property-block 322856 121.21322218 0.0003754405
org-macro-replace-all 2 112.94112931 56.470564655
org-element-context 8588 107.43778316 0.0125102216
org-element-at-point 8976 101.79823538 0.0113411581
org-element--current-element 236519 91.414278451 0.0003864986
org-up-heading-safe 263822 84.507423221 0.0003203198
org-element--parse-elements 3113 40.774293673 0.0130980705
org-back-to-heading 1209279 40.394825581 3.340...e-05
org-element-headline-parser 59033 32.808386543 0.0005557634
org-before-first-heading-p 272799 32.791086826 0.0001202023
org-list-struct 8035 20.801415973 0.0025888507
org-element-map 19598 20.466600874 0.0010443208
org-latex-link 341 19.91215084 0.0583934042
org-export-resolve-fuzzy-link 281 19.879402747 0.0707452055
...
Functions taking less than 15 seconds cumulative time elided.
--
Lawrence Mitchell <wence@gmx.li>
next prev parent reply other threads:[~2013-05-06 16:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 19:28 Exporting large documents Achim Gratz
2013-04-27 19:35 ` Carsten Dominik
2013-04-29 16:04 ` Lawrence Mitchell
2013-04-29 18:44 ` Achim Gratz
2013-05-01 12:18 ` [PATCH] ox: Cache locations of fuzzy links Lawrence Mitchell
2013-05-01 21:46 ` Nicolas Goaziou
2013-05-02 9:03 ` [PATCH v2] " Lawrence Mitchell
2013-05-02 12:35 ` Nicolas Goaziou
2013-05-02 12:53 ` Nicolas Goaziou
2013-05-03 8:43 ` Exporting large documents Carsten Dominik
2013-05-03 11:12 ` Lawrence Mitchell
[not found] ` <877gjfgnl9.fsf@gmail.com>
[not found] ` <0F877AB5-D488-4223-B0E7-F11B4B973614@gmail.com>
[not found] ` <87ip2xfd0x.fsf@gmail.com>
2013-05-06 11:07 ` Lawrence Mitchell
2013-05-06 16:15 ` Lawrence Mitchell [this message]
2013-05-07 10:26 ` Bastien
2013-05-06 18:41 ` Achim Gratz
2013-05-06 19:17 ` Nicolas Goaziou
2013-05-06 19:32 ` Achim Gratz
2013-05-07 14:29 ` Nicolas Goaziou
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=878v3sxeyc.fsf@gmx.li \
--to=wence@gmx.li \
--cc=emacs-orgmode@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/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).