I can’t time report loading on my macs in 2.7.3 — gnucash crashes whenever I 
try to create a report. No problems or slowdowns with 2.6.19
--
Dave Reiser
dbrei...@icloud.com





> On Jan 27, 2018, at 11:39 AM, R. Victor Klassen <rvklas...@gmail.com> wrote:
> 
> This is quite dramatic.  Probably my favourite thing to do in code is to make 
> it faster.  (Un)fortunately I don’t run Windows, so I have little to offer 
> here.  The sudden and dramatic change raises the question of what changed?   
> And I haven’t noticed this issue on the Mac, so I’m guessing the change was 
> only on Windows.  Which in itself supports the theory that the change 
> happened not within GnuCash but in one of its dependencies.  
> 
> But then, I try hard never to close GnuCash down, so I’m not sure I would 
> have noticed.   
> 
> The subject line refers to reports - the sample being tested has many large 
> reports open at startup, as I understand it.   But if “Loading User Data” 
> precedes the start of building reports, it wouldn’t seem that’s the issue - 
> unless building open reports is part of “Loading User Data”...
> 
> I’d be curious whether the startup time on an Sqlite3 file format would show 
> the same pattern.
> 
> 
>> On Jan 26, 2018, at 1:00 AM, David Carlson <david.carlson....@gmail.com> 
>> wrote:
>> 
>> Here are the times to fully open my data file on my Windows 7 laptop.
>> 
>> 2.6.18 to open 6,480 KB compressed XML file on C: drive
>> 3:14:21
>> 2.6.16 to open 82,605 KB uncompressed XML file on C: drive
>> 3:06:97
>> 2.6.18 to open 6,480 KB compressed XML file on LAN mapped to U:  3:54:00
>> 
>> 2.7.3 to open 6,484 KB compressed XML file on C: drive
>> 6:36:85
>> 2.7.3 to open 80,747 KB uncompressed XML file on C: drive
>> 6:41:29
>> 2.7.3 to open 6,484 KB compressed XML file on LAN mapped to U:    7:25:00
>> 
>> For release 2.7.3 it takes just over 4 minutes to finish 'Loading User
>> Data" and start building register tabs in the main window.  Release 2.6.18
>> took about 1 minute 50 seconds to finish 'Loading User Data" and start
>> building register tabs in the main window.
>> It looks like that part of the process is the first place to look for ways
>> to speed it up.
>> 
>> I am not sure why the uncompressed file loaded more slowly with 2.7.3.  I
>> did change the date of one transaction to make the file 'dirty' to get it
>> saved in uncompressed format.
>> 
>> Also, I think it is known that release 2.7.3 is unable to install F::Q,
>> even via the manual program link in the GnuCash program group of the
>> Windows 7 start menu.
>> 
>> David C
>> 
>> On Thu, Jan 25, 2018 at 6:35 PM, John Ralls <jra...@ceridwen.us> wrote:
>> 
>>> David,
>>> 
>>> Maybe just to rule it out as an issue you could temporarily put it on a
>>> local drive.
>>> 
>>> How big is it? It's XML, right? See if turning compression on or off makes
>>> a difference.
>>> 
>>> Regards,
>>> John Ralls
>>> 
>>> 
>>>> On Jan 25, 2018, at 3:15 PM, David Carlson <david.carlson....@gmail.com>
>>> wrote:
>>>> 
>>>> I failed to mention that my data file is not on my "C" drive, it is on a
>>>> LAN file-server, but the entire path is via 100 MHz Ethernet, no Wi-Fi.
>>>> 
>>>> David C
>>>> 
>>>> On Thu, Jan 25, 2018 at 2:45 PM, David Carlson <
>>> david.carlson....@gmail.com>
>>>> wrote:
>>>> 
>>>>> Preliminary results comparing release 2.6.18-3 with 2.7.3 on a Dell
>>>>> Precision 7510 laptop running Windows 7 sp1 64 bit with a Intel(R)
>>> Core(TM)
>>>>> i7-6820HQ CPU @2.70Ghz and 24.0 GB installed RAM and all updates
>>> installed
>>>>> except a recent Dell display driver update and the Spectre patch update
>>> is
>>>>> not installed yet(?):
>>>>> 
>>>>> Opening a copy of my current data file with scads of tabs including
>>>>> several reports, and a read-only register tab.
>>>>> 
>>>>> In 2.6.18-3 it took 3 minutes 54 seconds to complete opening the file
>>> with
>>>>> no Since Last Run interruption.
>>>>> 
>>>>> In 2.7.3 first touch it took 8 minutes 25 seconds to the metadata
>>> migrated
>>>>> window.
>>>>> 
>>>>> Second opening 7 minutes 5 seconds.  I have many more details to share
>>>>> elsewhere.
>>>>> 
>>>>> David C
>>>>> 
>>>>> 
>>>>> On Thu, Jan 25, 2018 at 1:09 PM, Geert Janssens <
>>>>> geert.gnuc...@kobaltwit.be> wrote:
>>>>> 
>>>>>> Op donderdag 25 januari 2018 17:17:48 CET schreef David Carlson:
>>>>>>> About not seeing Geert's message in the Gmail instance in Firefox on
>>> my
>>>>>>> laptop, on that machine gmail put it into spam because it did not meet
>>>>>>> their lofty standards for authentication.  On the Gmail app on my
>>>>>> Samsung
>>>>>>> phone, it was in the Inbox.  Most of Geert's other messages this
>>> morning
>>>>>>> went to my inbox on the laptop.  Go figure!?!  🤔
>>>>>>> 
>>>>>>> David C
>>>>>>> 
>>>>>> Yeah, I don't know what I ever did to upset Google that much they want
>>> to
>>>>>> delegate me to the spam box... I tried to say I'm sorry but they didn't
>>>>>> want
>>>>>> to hear it ;)
>>>>>> 
>>>>>> Geert
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>> _______________________________________________
>>>> gnucash-user mailing list
>>>> gnucash-user@gnucash.org
>>>> 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@gnucash.org
>> 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@gnucash.org
> 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@gnucash.org
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.

Reply via email to