I've only currently used workers in 2 places although i must say they do help a lot.
One is a simple rolling log file manager, where it logs info to a file and zips up old files etc. The other is loading a compressed dictionary file and parsing its contains for a spell checking (this is quite complexed as it matches rules to build full words, i'm parsing a hunspell dictionary). I did originally write the dictionary parser to be "friendly" and only process x amount of data per frame using loops to try and not block the ui, but since fp 11.5 i've been using it as a worker and its so much faster If you can target fp 11.5 or above i would highly recommend workers I love adobe scout its so helpful trying performance. Although the Flash builder profiler is still great, i find that much more useful for trying to find memory leaks On 27 July 2013 13:08, Ajar <[email protected]> wrote: > Hi Mark > thank you for your answer > Scout is a great idea, I'll loo into it. > I'm glad you suggested workers as this is a good opportunity to find out if > they can help in these sort of tasks... > I'm under the impression that workers were created to offload heavy > processing that can run asyncroneously like encoding of a file... > The typical tasks that run in a web app are > > - getting data from remote services, some queries are obvious and some > unique. > - parsing data coming back and rendering it in complex custom > components ? > - manage interactivity and navigating the app. > - caching? > > are any off those a good candidate for workers? > > would love to get your feedback > cheers > Ajar > > > > On Sat, Jul 27, 2013 at 10:26 AM, Mark Line <[email protected]> wrote: > > > I found adobe scout really useful to find performance issues, pretty easy > > to > > see where the frame time is going over. > > > > You could try and put sections of code into workers? > > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] On Behalf Of > > Ajar > > Sent: 27 July 2013 05:27 > > To: [email protected] > > Subject: Re: non-blocking preloading animation? > > > > Thanks for that Alex. > > :) > > > > On Fri, Jul 26, 2013 at 10:58 PM, Alex Harui <[email protected]> wrote: > > > > > > > > > > > On 7/26/13 12:31 PM, "Ajar" <[email protected]> wrote: > > > > > > >Hi all > > > >I have a big flex web project > > > >It takes a while to load.... its around 3M for the main app swf and > > > >80K for additional 4 modules that loads afterwords The loading weight > > > >is not bothering me, as we have this tiny animation with gags for the > > > >user to go through, it's not terrible. > > > >What bothers me is that once the app swf loads, everything chokes and > > > >freeze, until the app initializes itself. > > > >So I can't go the "perceived performance" way really because whatever > > > >I put there freezes and chokes for good 30 seconds... > > > >I even tried putting the preloader animation in a separate > > > >light-weight flash swf and have it in a separate div on the html on > > > >top at the center of the page. > > > >it behaves just the same. it doesn't matter if its in a different > > > >swf, it chokes just the same... > > > >Does workers relevant for this kind of scenario? > > > >Is there anything that comes to mind I could do beside re-writing the > > > >application? > > > Well, it depends on what you mean by 're-write'. Use the profiler to > > > see where all of the time is going. Some of those application > > > frameworks being discussed in the other thread can contribute to the > > > problem by doing their injections on creationComplete. > > > > > > Another app I analyzed was using creationPolicy=all everywhere. Sure, > > > it makes your code easier to write, but then that's the price you pay. > > > Think "on-demand" and "just-in-time", not "just-in-case". > > > > > > >:) > > > >cheers > > > >Ajar > > > > > > > > > > >
