[GNC] Delay during data entry

Tue May 7 20:37:27 EDT 2024

Windows 10 is fully 64-bit just like Windows 11, there's no difference 
in how they handle RAM. The different flavors of each version of Windows 
(Home, Pro, Enterprise, etc.) have different maximum amounts but they 
are the same for 10 vs. 11. I have Pro which has support for a maximum 
of 2 TB installed. The Home versions have a maximum of 128 GB.

I do have autosave turned on but the frequency is set for 5 minutes so 
that shouldn't be interfering with several back to back entries that 
only take 5 to 10 seconds to enter.

As for why I'm using Version 4.12, because it works for what I need and 
upgrading is painful because the customizations I made (for example, 
theming the program to make it dark) doesn't transfer easily. As far as 
I can tell there's nothing in the change logs for later versions there 
is nothing that appears to affect me directly so I don't see a need to 
change. I don't use the online quote functions, nor the business 
functions, and I rarely run reports so the default reports seem to be fine.

On 2024-05-06 03:48, Maria Inmaculada de la Torre wrote:
> Hello All,
> 
> I am running Windows 11 with 16Gb of RAM and Gnucash Build ID: 5.6+. The
> only time I notice some delays during data entry is when it is doing
> autosaves and in this version I'd say it is more like 1 or 2 seconds at
> most (older versions in Windows 10 had maybe a 3 or 4 seconds delay at
> most). Can Windows 10 even handle that amount of RAM properly? and why are
> you running such an old version of Gnucash in that machine?
> 
> Thanking you.
> 
> Regards,
> 
> 
> Inma
> 
> 
> On Sun, 5 May 2024 at 21:57, AC <gnucash at acarver.net> wrote:
> 
>> No, I do mean 128 GB RAM. Storage is 20 TB locally and 160 TB on the
>> network (but the data for Gnucash is stored on the local disks). It's
>> one of three daily drivers, this one being the Windows one for some CAD
>> software and MS Office.
>>
>> There's no latency anywhere else on the system, just in Gnucash after
>> I've entered a transaction and it does its own processing in the
>> background.
>>
>> On 2024-05-02 01:49, WR D wrote:
>>> 128GB of ram?  Can I assume you actually mean disk storage, not "RAM",
>> or that's one beast of a machine.
>>>
>>> I use the default install of Gnucash for windows (latest stable version)
>> - my local drives are NVME M.2 - so reasonably fast to boot up typically.
>>>
>>> My Gnucash file is 3.5MB and my Win 11 desktop is about 3 years old with
>> 16GB RAM and  Intel i5-9500 @3Ghz (in-built graphics).   I see variable 1-2
>> seconds delay while entering transaction data ... just enough to annoy me
>> as I don't notice it with any other software.
>>>
>>> I just put it down to the gnucash software, and not my hardware.  For
>> example I run MS Office 2021 software without noticeable delays while
>> inputting.
>>>
>>>
>>> -----Original Message-----
>>> From: gnucash-user <gnucash-user-bounces+dullege=hotmail.com at gnucash.org>
>> On Behalf Of AC
>>> Sent: Thursday, 2 May 2024 5:13 PM
>>> To: GnuCash users group <gnucash-user at gnucash.org>
>>> Subject: Re: [GNC] Delay during data entry
>>>
>>> On the machine running Gnucash it's a Win 10 with 128 GB of RAM. I'm
>> using version 4.12 with build ID 4.12+2022-09-24. According to the system
>> profiler the entire Gnucash process is occupying about 175 MB working set
>> RAM (physical in use), 119 MB active primary RAM (physical unable to be
>> used by other processes), 56 MB shared RAM, and 550 MB commit size
>> (allocated virtual by OS). I do notice a slightly higher cycle time
>> compared to other idle programs (most idle programs use 0 to
>>> 1 cycles while Gnucash is using 4 to 5 when idle).
>>>
>>> I do not use an SQL backend and I don't have compression turned on. The
>> current file size is around 42 MB. It's on a spinning SAS drive local to
>> the computer so I'm not dealing with network latency (though with no SQL
>> backend it's entirely RAM transaction anyway).
>>>
>>> On 2024-05-01 16:28, David Carlson wrote:
>>>> Those of us who are still running versions as old as 4.8, possibly
>>>> because we are not ready to tackle setting up a flatpak in Linux still
>>>> see horrible response times.  It gets worse when the data file when
>>>> loaded takes up over half of the RAM in our machine or if we are
>>>> running it in a virtual machine.  My version 4.8 Gnucash instance
>>>> takes about 11.3 Meg when saved or 2.4 Gig of RAM when loaded in Linux
>>>> Lite 6.6.  The entire virtual machine has 8 Gig of RAM but every time
>>>> I press enter it takes several seconds before the curser returns, or
>>>> 15 seconds or more when I execute File >Save, which needs to be done
>>>> every few minutes.  Some of the delay comes from having too many
>>>> registers open.  I realize most of my misery is self inflicted, since
>>>> I have now tried working on the same data in release
>>>> 5.6.1 on a Windoze 10 machine with 32 Gig RAM, which almost keeps up
>>>> with my slow typing.  It is still going to take a while to revise my
>>>> procedures to get away from GnuCash release 4.8 and have the level of
>>>> hardware and software redundancy that I want to keep backups, etc.
>>>>
>>>> On Wed, May 1, 2024 at 4:36 PM R Losey <rlosey at gmail.com> wrote:
>>>>
>>>>> I don't see any delays on either Windows (Win 10, 16G RAM), or my M1
>>>>> iMac (Sonoma 14.4.1; 16G RAM), or or Linux (Ubunto 22.04LTS, 8G RAM).
>>>>> In all cases, the file is stored on my NAS with spinning hard drives
>>>>> (that is, not an SSD), and I am saving to a compressed file (I've not
>>>>> changed this since I started, so I assume that these are the default
>>>>> settings).  My file size is about 2.2M
>>>>>
>>>>> Could it be that you are saving to a SQL database? I remember reading
>>>>> here that (unlike the standard option) it saves after every
>>>>> transaction. Maybe the database is on a slowish drive?
>>>>>
>>>>> Otherwise, I don't know why there would be such a lengthy delay after
>>>>> doing an entry.
>>>>>
>>>>> I assume you've run the Check/Repair just to verify that there isn't
>>>>> some file problem?
>>>>>
>>>>>
>>>>>
>>>>> On Wed, May 1, 2024 at 12:00 AM AC <gnucash at acarver.net> wrote:
>>>>>
>>>>>> Just as a curiosity what is going on under the hood that influences
>>>>>> the delay after entering data into a register row? I notice that
>>>>>> after I enter the details of a transaction into a register and
>>>>>> commit the changes (pressing enter or tabbing to next row) there is
>>>>>> a 5 to 7 second delay before I can enter the next transaction.
>>>>>> _______________________________________________
>>>>>> 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.
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> _________________________________
>>>>> Richard Losey
>>>>> rlosey at gmail.com
>>>>> Micah 6:8
>>>>> _______________________________________________
>>>>> 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.
>>
>> _______________________________________________
>> 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.
>>
> 