'Saves' with SQLite are supposed to be instant. That is, all commits on changes happen right away, not on a schedule or only on exit. (same with the other two db backends, and those are more difficult to manage/administer)

If you've removed Piecash temporarily from the workflow, and it still takes that long to exit, something else is amiss.

Do you have a very large number of tabs open when you exit? (such as 25+ reports? This has known to cause slow or hanging re-starts for some reports, but perhaps shutdown can be affected as well.)

Note, I'm on an older '13 Mini with BigSur, but my file is only 16.5MB, so I can't speak file size alone.

Another variable is the M1. While allegedly non-optimized apps should at least run as well as on Intel, perhaps some things don't translate well—but I'm way out of my depth there—just hazarding a guess.

Regards,
Adrien

On 5/9/22 2:18 AM, Tim Hume via gnucash-user wrote:
Hi people,

I guess the underlying issue is probably Piecash - or possibly the way it 
interacts with SQLite. Though GnuCash itself is pretty slow at exit time too 
(maybe 30 seconds to a minute) - but not in the same league of slowness as my 
Python program using Piecash.

I was simply hoping that maybe someone else had experienced this and might have 
some tips - I realise this mailing list is for GnuCash, but given Piecash is 
used for manipulating GnuCash files, the thought occurred that others on the 
list may have some tips. The MySQL/PostgreSQL suggestion may be a good one. But 
before I go down this track I'll a browse though the Piecash code.

I'll report back if I find anything or have success in speeding things up.

_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to