ID caching: how to test?

J. Landman Gay jacque at hyperactivesw.com
Fri May 10 23:07:38 CDT 2013


On 5/10/13 9:11 PM, Richard Gaskin wrote:
> The Release Notes for v6 include:
>
>    ID caching (6.0 DP 2)
>    New global property – allowDatagramBroadcasts (6.0 DP 2)
>    A new global property allowDatagramBroadcasts has been added. This
>    needs to be set to true before sending to a broadcast address
>    (enables the per-socket flag for whether they are allowed).
>    The engine now caches lookups of control references of the form
>    “card id ...” and “control id ...”.
>    This speeds up any access using those forms after the first time,
>    turning an operation that would be completed in linear time into
>    one that will be completed in constant time.
>
>
> I'm not clear on the syntax, so I've been unable to benchmark the
> performance boost.

I think the datagram stuff and the image caching are two different 
things (if it's in the docs that way, it looks like a misplaced heading 
to me.) The image caching just happens automatically. Benchmarking would 
involve timing a procedure in 5.5.4 and then repeating it in 6.0.1 to 
see the difference.

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com




More information about the use-livecode mailing list