Go to card has become slow

[Ralph DiMola]

On Windows I have seen a slow down on some but not all cards when the SE is open. Close the SE and everything speeds back up. 

Ralph DiMola
IT Director
Evergreen Information Services
rdimola at evergreeninfo.net


-----Original Message-----
From: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] On Behalf Of Terence Heaford via use-livecode
Sent: Friday, April 03, 2020 8:55 AM
To: How to use LiveCode
Cc: Terence Heaford
Subject: Re: Go to card has become slow

I have now copied the modified scripts from the project version that was slow and reapplied them to the previous version which was running fast.

Applying the modified scripts has not resulted in any slowdown of the version they have been applied to.

So, I cannot understand why the project slowed down in the first place but…

all is now well until it happens again.


Thanks

Terry

> On 3 Apr 2020, at 09:42, Mark Waddingham via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> On 2020-04-03 09:25, Terence Heaford via use-livecode wrote:
>> Fortunately I have Time Machine running on my mac.
>> I have gone back to a previous copy from the 01 April 2020 and this 
>> project is running at full speed.
>> I have made no modifications to the underlying functionality of this 
>> project other than some modifications to SQLite scripts to improve 
>> performance.
>> I will make those adjustments again and report on the outcome.
>> I do not believe it’s anything I have done.
> 
> I'd humbly  suggest that modifications to SQLite scripts constitute 
> modifications ;)
> 
> Have you modified the SQLite database in any way?
> 
> Like most db's SQLite is heavily dependent on indices to prevent operations being slow - if some have been removed which existing queries relied upon, or one hasn't been added to support a new/modified query then that could cause a heavy performance loss.
> 
> Similarly, SQLite is transactional, so if you do lots of mutation queries outside of one each individual query will take a lot longer (as each will be under its own transaction requiring a OS disk flush/sync after each) - if you've tweaked how you are doing such queries and not taken into account transactions that could also cause a heavy performance loss.
> 
> Warmest Regards,
> 
> Mark.
> 
> --
> Mark Waddingham ~ mark at livecode.com ~ http://www.livecode.com/
> LiveCode: Everyone can create apps
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode