From: Timothy <tecosaur@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [ANN] An Org parser for Julia
Date: Thu, 02 Dec 2021 18:30:24 +0800 [thread overview]
Message-ID: <87ilw7p9re.fsf@gmail.com> (raw)
In-Reply-To: <87k0gn71uz.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1601 bytes --]
Hi Ihor,
> I am wondering how the third-party parsers are going to scale for larger
> Org files. I did some simple testing in the past, and it seems that only
> tree-sitter can potentially get sufficiently close to org-element in
> terms of performance.
I’ve actually had a brief look at my performance using my Emacs config file
(which is ~10k lines). On this, my parser is about ~5x faster than org-element.
On a smaller file like the project’s readme it’s closer to ~10x faster. I’ve
also noticed that I can multithread the parsing, which produces a ~9x speedup on
my computer. So, that would be ~40-90x faster than org-element. I have yet to do
much profiling/benchmarking/optimisation though, I’m still in the “feature
adding” phase. This means that it could well slow down as I add more for it to
recognise, but there are probably also unrealised potential performance
improvements.
> Maybe we should implement a Elisp LSP server instead of many individual
> parsers in different languages?
For the sake of tools that operate on Org files, not just the Org editing
experience, I think it’s quite good if we have a selection of /good/ parsers
available for different languages. However, I also think an LSP server would be
good. That’s why I have <https://github.com/tecosaur/org-lsp>, even if I haven’t
spent anywhere near as much time on it as I would like (it’s barely a skeleton
at the moment).
> tree-sitter vs. org-element on 15M Org file
Might you have a link to this file? I’d be interested to try it.
All the best,
Timothy
next prev parent reply other threads:[~2021-12-02 10:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 9:06 [ANN] An Org parser for Julia Timothy
2021-12-02 10:11 ` Ihor Radchenko
2021-12-02 10:30 ` Timothy [this message]
2021-12-02 11:13 ` Ihor Radchenko
2021-12-02 11:20 ` Timothy
2021-12-02 12:07 ` Ihor Radchenko
2021-12-02 12:11 ` Timothy
2021-12-02 12:18 ` Eric S Fraga
2021-12-02 14:04 ` Timothy
2021-12-02 15:56 ` Eric S Fraga
2022-09-25 8:02 ` Bastien
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=87ilw7p9re.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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).