From: Alan <omvvardar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: new citeproc performance notes
Date: Sat, 12 Sep 2020 16:29:14 -0700 (PDT) [thread overview]
Message-ID: <52149bdb-e476-4013-8d5b-72b0b0544877n@googlegroups.com> (raw)
In-Reply-To: <m2k0wyioij.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1166 bytes --]
Great! Can we try it? Or it's not yet in public version?
On Sunday, September 13, 2020 at 1:06:30 AM UTC+2 John MacFarlane wrote:
>
> I tried out the new citeproc-enabled pandoc (from citeproc
> branch), comparing it against pandoc 2.10.1 + pandoc-citeproc.
>
> My test project was a document with about 30,000 words,
> using a 132K bibtex bibliography.
>
> In addition to pandoc-citeproc, I used a lua filter to
> count words.
>
> For pandoc 2.10.1 + pandoc-citeproc, the build (to HTML)
> took 2.22s.
>
> With the new citeproc-enabled pandoc, it took 1.03s.
> By comparison, without --citeproc (skipping citation processing)
> it took 0.84s. So, the overhead for citation processing is now
> pretty minimal, and people should see a big speedup.
>
>
>
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/52149bdb-e476-4013-8d5b-72b0b0544877n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1732 bytes --]
next prev parent reply other threads:[~2020-09-12 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 23:06 John MacFarlane
[not found] ` <m2k0wyioij.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-09-12 23:29 ` Alan [this message]
[not found] ` <52149bdb-e476-4013-8d5b-72b0b0544877n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-13 5:18 ` John MacFarlane
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=52149bdb-e476-4013-8d5b-72b0b0544877n@googlegroups.com \
--to=omvvardar-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).