There might be some tasks which you set on the idle queue which are
sitting around eating cycles,
you could put a print tool like this to tell you if there is stuff sitting there
<text>
<handler name="onidle" reference="lz.Idle">
setAttribute('text', lz.Idle.onidle.delegateList.length - 1)
</handler>
<handler name="onclick">
Debug.write("%w", lz.Idle.onidle.delegateList);
</handler>
</text>
On Mon, Mar 9, 2009 at 5:49 PM, Charles Watt <[email protected]> wrote:
> I have a pretty large Laszlo app that puts a hefty strain on the CPU. At
> rest -- i.e., no data updates in progress, no network interactions, no user
> interactions via keyboard or mouse, no visible activity on the screen -- it
> consumed a full 99+% of the CPU such that the application would appear to
> lock up for 5 - 10 seconds at a time. After removing several complex
> constraints, this is now down to about an 80% CPU load. There just aren't
> enough constrains left to account for this load. However, I do use
> width="100%" all over the place. Are these evaluated continuously like a
> constraint? Any other suggestions on where to look? Unfortunately SWF 7 is
> out and I and have several issues to correct before I can get a clean
> compile in DHTML, so I'm stuck without a profiler.
>
> Thanks,
> Charlie Watt
> Racemi
>
--
Henry Minsky
Software Architect
[email protected]
