From: Samuel Wales <firstname.lastname@example.org>
To: Ihor Radchenko <email@example.com>
Cc: firstname.lastname@example.org, David Masterson <email@example.com>
Subject: Re: archiving speed [was Re: Tips on maintaining history in Org Mode]
Date: Wed, 11 Aug 2021 22:47:40 -0700 [thread overview]
Message-ID: <CAJcAo8vjMxTKYqs3j5XkJq7p+efRo9xudH2tZL18E4AOG6GYzQ@mail.gmail.com> (raw)
i will give up on archiving categories if needed to make archiving be
practical. will ahfe to try it as soon as i can.
On 8/11/21, Ihor Radchenko <firstname.lastname@example.org> wrote:
> Samuel Wales <email@example.com> writes:
>> thanks for the clarification. are you saying that, for every archived
>> entry, it calculates teh category property, using the original org
>> file, in order to add a category property to just one archived entry?
> Nope. It does not just calculate category for the archived entry, but
> re-calculates all the category properties in the original Org file
> (updating category cache).
>> that would certainly slow down more and more, but it sends me back to
>> my question about whether append to file would work.
>> i.e. build the single entry in a temporary buffer then write that
>> region to a file on disk.
> Appending can indeed work if your archive location is at the end of the
> file. However, it is not necessary the performance bottleneck. Certainly
> not when the archive file is small.
The Kafka Pandemic
Please learn what misopathy is.
next prev parent reply other threads:[~2021-08-12 5:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 4:22 archiving speed [was Re: Tips on maintaining history in Org Mode] Samuel Wales
2021-03-01 6:02 ` Ihor Radchenko
2021-08-11 1:08 ` Samuel Wales
2021-08-11 4:13 ` Ihor Radchenko
2021-08-11 5:58 ` Samuel Wales
2021-08-11 6:43 ` Ihor Radchenko
2021-08-11 22:23 ` Samuel Wales
2021-08-12 0:24 ` Ihor Radchenko
2021-08-12 5:47 ` Samuel Wales [this message]
2021-08-12 3:38 ` Tim Cross
2021-08-12 5:49 ` Samuel Wales
2021-08-12 5:56 ` Tim Cross
2021-10-17 12:08 ` Ihor Radchenko
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).