Slow launch times on Windows 7
zryip.theslug at gmail.com
Thu Sep 16 17:49:14 CDT 2010
On Thu, Sep 16, 2010 at 11:27 PM, zryip theSlug <zryip.theslug at gmail.com> wrote:
> On Thu, Sep 16, 2010 at 10:33 PM, Giovanni Cannizzaro
> <johncanmail-all at yahoo.it> wrote:
>> Il 16/09/2010 20.42, zryip theSlug ha scritto:
>>> On Thu, Sep 16, 2010 at 7:56 PM, tekne<tekne at gruppoparentesi.it> wrote:
>>>> In my app I have about 130 substacks with an image substack and a lot of
>>>> stack using datagrid. (rev file is about 45 MB)
>>>> NO problem in the IDE and with the standalone in Mac, Linux and in WIN
>>>> pre 7
>>>> version (also with Vista)
>>> Try to expertise the alwaysBuffer property of each substacks of your
>>> For doing that, execute a script like this one in the main stack:
>>> repeat for each line tSubstack in the substacks of this stack
>>> put tSubstack&& the alwaysbuffer of stack tSubstack of this
>>> stack& cr after msg
>>> end repeat
>>> If the alwaysBuffer property of several of the substacks is set to
>>> true, try to set them to false and launch again.
>>> Check also the alwaysBuffer property of your images
> I'm not an italian speaker so I'm going to reply in english.
>> a parte il fatto che non ho capito bene esattamente a cosa serve questa
>> proprietà (la guida non è molto chiara al riguardo) ho fatto uno scriptino
>> per settarla a false su tutti gli stack e su tutte le immagini di tutte le
>> card di tutti gli stack.
> The alwaysbuffer property corresponds to the checkbox "Preload in
> memory". You have this checkbox for image and the property exists also
> for stacks. In my knowledge this property doesn't exists for card.
> To win performances in using stacks, images and probably objects,
> Runrev preload them in memory. I'm not a specialist of this, and you
> could have better and accurate explanation of this property by more
> experienced members of this list.
> By default the alwaysbuffer property of a new stack or a new image, is
> set to false
>> Il fatto è che non so bene interpretare gli effetti...
>> Mentre sotto Vista il tempo si caricamento è drasticamente sceso (in 3
>> tentativi di avvio) da 31 secondi a 16 (il 50%... mi sembra un ottimo
>> risultato) nella macchina virtuale con Seven ho ottenuto solo 30 secondi di
>> risparmio sui 4 minuti dell'avvio precedente. Solo un 12.5% di guadagno
>> temporale che però non so dire fino a che punto è reale data la "virtualità"
>> XD XD del mezzo di prova.
> If I understand well, by setting the alwaysbuffer to false :
> - in Vista you have reduced the start time by 50%
> - in Seven, 12,5%
> You run Seven on a virtual machine? VMWare, the Microsoft virtual
> machine or an other way?
> It seems to me that in a virtual machine, the memory allowed is
> managed differently.
> Have you tried in a native Seven?
>> Però potrebbe essere una base di partenza, volendo capire prima l'esatto
>> impatto di questa proprietà sul software.
> I'm not going to speculate. I will let the people who have more
> experience than me answer. I thought to the "preload in memory"
> property more by feeling than by experience.
> I hope that it will be a good start to solve your problem.
That seems not logical here if your problem could be solved by a new
installation of Seven and not by a code modification.
With the alwaysBuffer property we have a clue that the problem could
be linked to how the memory is managed by Seven, or/and by Rev in
Is it a Seven 64bits or 32bits?
Have you checked the RAM of your PC?
In Seven (and Vista as well) you can check the RAM by executing the "MdSched"
command. This tool is also available in the admin tools of windows. Not sure
of the name of the application. I have no Seven at this moment
-Zryip TheSlug- wish you the best! 8)
More information about the use-livecode