[GNC] GnuCash Delays on KB Input

[Fross, Michael]

Agreed with the size issue.  The compression does make a big difference.
My data file using compressed xml is 2.6M.  Uncompressed XML is 37.6M.  I'm
not sure how that translates to SQL, but it is uncompressed so I assume the
size would be in the ballpark of 37M.

Michael

On Tue, Aug 26, 2025 at 5:32 PM sunfish62--- via gnucash-user <
gnucash-user at gnucash.org> wrote:

> I actually tried that. The results were inconclusive.
>
> Aside: the sqlite file was 58mb, and it's not clear to me that a sql file
> format would improve things if size were the issue, since GnuCash loads
> everything into memory at startup. I'm also not enamored of the sql back
> end because of the sheer size of everything on disk this way.
>
> ⁣David T.​
>
> On Aug 26, 2025, 2:11 PM, at 2:11 PM, Cam Ellison <cam at ellisonet.ca>
> wrote:
> >On 2025-08-26 10:29, David T. via gnucash-user wrote:
> >> Given Stan's response on this, I'm imagining the problem lies with
> >> something in the data file. In fact, if I open a different file on
> >the
> >> machine, the problem appears to have disappeared. So, that supports
> >> the idea that there is something wrong with the file.
> >>
> >>
> >> Unfortunately, my data file covers 20 years of information. And yes,
> >> I've run Check & Repair on the whole file. I can also eliminate any
> >> issue with the gcm file, since I am on a new machine, and the gcm is
> >> new (I know this because every account's column settings are
> >defaulted
> >> back stock layout. I had set the columns on the old machine).
> >>
> >>
> >> I have absolutely no idea how I would troubleshoot this. Re-entering
> >> 20 years of data is not the answer. As for an older backup, I had
> >> already held off on bookkeeping for the last six months; going
> >further
> >> back would entail manual entry of thousands of transactions, which is
> >
> >> really not something I'm prepared to do either.
> >>
> >>
> >> I would scan the raw xml to see if there were something obvious, but
> >I
> >> don't even know what I'd be looking for. I am considering exporting
> >> the entire file to CSV and then reimporting into a new file,but
> >again,
> >> if the problem is some form of corruption in the transaction data,
> >> this would just propagate the problem in a new file...
> >>
> >>
> >> I am open to creative suggestions.
> >>
> >Are you in a position to switch to a database (postgresql, mysql,
> >sqlite)? The problem may be (in part or whole) the sheer size of the
> >file, not its contents or structure.
> >
> >Cheers
> >
> >Cam
> >
> >
> >_______________________________________________
> >gnucash-user mailing list
> >gnucash-user at gnucash.org
> >To update your subscription preferences or to unsubscribe:
> >https://lists.gnucash.org/mailman/listinfo/gnucash-user
> >-----
> >Please remember to CC this list on all your replies.
> >You can do this by using Reply-To-List or Reply-All.
>
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>