> Or are people running each query as a separate Beancount invocation from 
scratch?

How else would you do it? Do you never script anything? Every query you 
make is done manually from the bean-query repl?

I have a script that runs:

- bean-download needs-update (a 3rd party script, I can't get all the 
context sitting in the engine)
- beangulp to import things (ditto, plus "extract" and "archive" operations 
requires 2 separate invocations)
- autobean-format (though I don't think this actually uses beancount to 
load entries and does its own thing)
- bean-price (another 3rd party script that requires yet another parsing of 
all entries)
- several bean-queries to sanity check various things (any flags with !, 
any vacation not in a leaf account, anything without a payee, etc)
- scripts that build spending trends, net worth trends, graph and chart 
things.

If each invocation of beancount to parse the entries costs 600ms my script 
can easily take 6+ seconds to run. That is tolerable but annoying when done 
on the command line but I've been converting it to a simple web-app to make 
things more visible for my wife and having to wait 6-10 seconds to load a 
web page is obviously ridiculous.

On Friday, March 20, 2026 at 3:26:07 AM UTC+10:30 [email protected] 
wrote:

> I have seen a number of people commenting that Beancount is too slow, and 
> there's a desire to see a faster implementation.
>
> I'm not really understanding why this is an issue. Can someone explain 
> please? 
>
> If you load your beanfile and run the plugins and booking algorithm so all 
> the context is sitting in the engine while you make a number of queries, 
> why does it matter if it takes a couple of seconds to be ready to answer 
> queries? 
>
> Or are people running each query as a separate Beancount invocation from 
> scratch?
>
> Or are some queries very slow in and of themselves?
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/beancount/ff7c7f58-c972-433a-b460-759a07e9d08an%40googlegroups.com.

Reply via email to