From: Milan Zamazal <pdm@zamazal.org>
To: emacs-orgmode@gnu.org
Subject: Re: org-drill extremely slow with Org 9.2.5
Date: Mon, 26 Aug 2019 21:39:11 +0200 [thread overview]
Message-ID: <8736hn67j4.fsf@zamazal.org> (raw)
In-Reply-To: CAA01p3oSSz_6-Qn4z7DvUSgamLJCKbN7PwBkj-Az_Ei23k4mkA@mail.gmail.com
>>>>> "OK" == Oleh Krehel <ohwoeowho@gmail.com> writes:
OK> I noticed org-drill being slow three years ago when I tried to
OK> learn it. So I wrote my own package:
OK> https://github.com/abo-abo/pamparam/. It's quite fast: it takes
OK> 0.6s to sync my 3300 cards from the master Org file. And
OK> day-to-day learning operations like building a schedule or
OK> fetching a card are instantaneous. The master file is
OK> relatively small, since it stores no metadata: less than 10000
OK> lines. The metadata is stored per-card, each card is in its own
OK> file. The whole thing is backed by Git. All your learning
OK> sessions are stored in commits as well.
OK> Check it out. It might have less features, but it's really fast
OK> and has served me well.
Hi Oleh, pamparam looks interesting, however the very first blocker of
adoption is that having to type the answers is slower than anything
else... And not always feasible.
Nevertheless the concepts behind pamparam are interesting. When I grep
all the :PROPERTIES: out of my org-drill file, Org can visit and
navigate the resulting file completely fine. So the problem is how Org
deals with its properties.
I can see two options:
a) to fix Org property processing
b) to change org-drill to off-load metadata to a separate file
I'm afraid b) alone wouldn't help, since when I retain just :ID:
properties, then the file is unusably slow in Org.
next prev parent reply other threads:[~2019-08-26 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 18:10 org-drill extremely slow with Org 9.2.5 Milan Zamazal
2019-08-25 20:30 ` Oleh Krehel
2019-08-25 22:37 ` John Kitchin
2019-08-26 19:39 ` Milan Zamazal [this message]
2019-09-15 14:13 ` Christian Heinrich
2019-09-22 17:57 ` Milan Zamazal
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=8736hn67j4.fsf@zamazal.org \
--to=pdm@zamazal.org \
--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).