From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Julian Scheid <julians37@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Fast JSON codec based on YAJL
Date: Mon, 14 Jan 2013 21:26:46 -0500 [thread overview]
Message-ID: <jwvzk0bnpws.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m2hamj8eq3.fsf@gmail.com> (Julian Scheid's message of "Tue, 15 Jan 2013 01:36:04 +0100")
> A few unscientific benchmarks suggest that YAJL (via my interface) is
> roughly 5 to 25 times as fast as byte-compiled json.el, on average about
> an order of magnitude faster. Memory usage is about on par.
You mean that json.elc is only 5 to 25 times slower than
a C implementation? I actually expected significantly worse.
Stefan
next prev parent reply other threads:[~2013-01-15 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 0:36 Fast JSON codec based on YAJL Julian Scheid
2013-01-15 2:26 ` Stefan Monnier [this message]
2013-01-15 3:04 ` Julian Scheid
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvzk0bnpws.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=julians37@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.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).