From: Ihor Radchenko <email@example.com>
To: Samuel Wales <firstname.lastname@example.org>
Subject: Re: [BUG] org-element-cache bug: org-persist-read persists seemingly forever
Date: Sat, 25 Dec 2021 23:43:27 +0800 [thread overview]
Message-ID: <87czlkadwg.fsf@localhost> (raw)
Samuel Wales <email@example.com> writes:
> 20051 135025 938122 other--a.org
> this is a smallish to middling file for me. my largest is 4x larger.
> i haven't gotten new org to work yet so i haven't revisited this yet.
This is odd. It only takes 2 sec to write caches for my largest 15Mb
file. Though I have SSD.
I just pushed a change to org-persist. Now, Org will show a message with
some info about read/write duration when the duration is >0.5 sec. If
you see messages from org-persist can you report them?
prev parent reply other threads:[~2021-12-25 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 1:26 [BUG] org-element-cache bug: org-persist-read persists seemingly forever Samuel Wales
2021-12-24 11:46 ` Ihor Radchenko
2021-12-24 23:06 ` Samuel Wales
2021-12-25 15:43 ` Ihor Radchenko [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).