An air program will process many log files, click run button to inspect these log files one by one.
*Problems*: Click run button, then the air program's performance is OK. Click run button again, then the air program's performance maybe OK or may not OK.(about 60-70% is NOT OK) Click run button again, then the air program's performance is OK. ... ... Seems only the second run may have the performance issue. So weird? In fact, each run should do the same thing. BTW, the busy cursor is a clock, when running slow, the clock cursor also run slowly. *About profiler*: And I also use Flex builder profiler to analyse. For example, for OK run, elapse time: 2min the biggest cumulative time: 1min for issue run: elapse time: 7min the biggest cumulative time: 3.5min *Questions*: 1. Do you have any general clue or hint on this issue? 2. About profiler, for example, the elapse time is 7min, but cumulative time is 3.5min, where is another 3.5min? seems some functions were not be counted by profiler? how can I know what costs the another 3.5 min? 3. *Backgrounds*: 1. Windows Vista, Flex builder3, flex sdk3.2, actionscript3 2. when processing log, read file, check each line for finding the keyword. 3. one virtual thread(by timer) is for one log file processing. 4: any other information need? Thanks.
