I actually have the same question. I have 20+ years worth of detailed expenses in beancount. Loading ledger without cash (on updated ledger) takes about 6 sec, with cash 1 sec.
And, as you said, once it is loaded (in beanquery, Fava or in a notebook ), all following analysis is quite fast. So, taking into account the Moor's law, I have decided, that beancount speed is not going to be a problem for me personally for the rest of my life. I definitely would not want it to be traded for breaking the API compatibility On Thursday, March 19, 2026 at 5:56:07 PM UTC+1 [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/18be428d-dbbe-4aca-8f0c-a36eaa14d5cdn%40googlegroups.com.
