Go to card has become slow

[Brian Milby]

I did 3 additional tests this morning and believe that the issue lies
somewhere in the de/encoding of text or the way that text is streamed to
the file.  My additional tests were using a non-shared text field (due to
the way the text of a shared field is stored in memory, was wondering if
that was a contributor - does not seem to be that significant), putting the
text into a custom property of the card, and setting the script of the card
to the text.  In each of these new tests, the time to save was very close.
The non-BG one was .55 seconds faster but that could just be an artifact of
not doing enough tests on each to get a solid average.

This does make looking into the source code a little easier though since we
can rule out something specific to the field object and can focus on what
is common between the different ways text is streamed to the file.

My tests were on a Win10 laptop (i5-6300 @ 2.4GHZ; 8GB RAM)

On Sat, Apr 11, 2020 at 8:55 AM Neville Smythe via use-livecode <
use-livecode at lists.runrev.com> wrote:

> Sorry Brian, I uploaded from the wrong folder. Here is the update test
> set. But the only difference is that you don’t need to hold down the shift
> key to see the binary save timing.
>
> https://www.dropbox.com/sh/cb2r9jbohxqv6bp/AAAQ1weLLlzrKYQ21yn1apf9a?dl=0
> <https://www.dropbox.com/sh/cb2r9jbohxqv6bp/AAAQ1weLLlzrKYQ21yn1apf9a?dl=0
> >
>
> Colin, the test set here shows the timing of saving of stacks; the times
> for Windows 10 are a large multiple of Mac/Unix and we discussing possible
> reasons before updating the bug report  bug 21305 <
> https://quality.livecode.com/show_bug.cgi?id=21305>  for Quality Control
>
> Neville
> _______________________________________________
> 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
>