Performance Mystery Solved - IT'S THE DATA STUPID!!

Peter Haworth pete at mollysrevenge.com
Thu Nov 11 19:28:48 CST 2010


Yes, that's what I'm seeing.  With the references to my .rev filepath  
in the control names, the card I'm using to test was taking around 35  
seconds to open.  I went through and manually removed the references  
to the filepath (that's the only thing I changed I swear!) and built  
the standalone again and now the card opens just about  
instantaneously.  So maybe there's a bug after all in that the .rev  
stack should only be loaded into memory at the first access to it but  
it's happening every time?

Whatever the issue, I have to change something because my standalone  
wouldn't run unless the .rev file was on the same computer and that  
doesn't make any sense.  I think I'm going to bite the bullet and  
change everything over to use control IDs instead of long names.

Pete Haworth

On Nov 11, 2010, at 5:12 PM, Monte Goulding wrote:

>> Unless you're explicitly purging the stacks, any access to a  
>> property of a stack file will load it into memory.  The first  
>> access will take a hit only if the stack isn't already in memory,  
>> but subsequent accesses should be about as fast whether referring  
>> to just the stack name or the stack file path, since they're  
>> interchangeable for mainstacks.
>
> Hi Richard
>
> I don't think this is entirely true. At least it wasn't when I was  
> working on the standalone builder all those years ago. There was a  
> massive difference in speed between looping over the controls of a  
> stack if that stack was invisible toplevel compared to just  
> referencing it as a filename. There was a user that was having  
> extremely slow builds because they had so many controls.
>
> Cheers
>
> Monte_______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>




More information about the use-livecode mailing list