Changes between Version 8 and Version 9 of GROUP_APP_PERFORMANCE_R0


Ignore:
Timestamp:
05/19/09 16:36:30 (16 years ago)
Author:
gogov
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TabularUnified GROUP_APP_PERFORMANCE_R0

    v8 v9  
    55= Analysis = 
    66== Overview == 
    7 The goal of this task is to improve the performance of the Sophie2 platform before the release at 2009-05-15. 
     7The goal of this task is to improve the performance of the Sophie2 platform before the weekly at 2009-05-19. 
    88 
    99== Task requirements == 
     
    1919 * usage of more efficient data structures at certain classes if possible and not much time needed to refactor 
    2020 
    21 Also some logging logic should be inculded which measures startup time so optimizations are with visible effect. 
     21Also some logging logic should be included which measures startup time so optimizations are with visible effect. 
    2222 
    2323== Task result == 
     
    5858 * I tried using several profilers, after all for now me and Milo decided to try writing a simple profiler ourselves. 
    5959 * I tried several quick low-level ProLib candidates for optimization which didn't actually help too much so I don't include them in the implementation. 
     60  * tried providing a swallow mode for the ProLib Registry. That is if swallow mode is on, no reads would get registered (which differs from the NoReadTrack-like behavior where no read are ''expected'' to be registered and an exception is thrown if a read tries to get registered). Didn't make a big difference, as expected. 
     61  * tried messing with filtering logic in the ProLib Registry.endReadTrack() method but also as expected it didn't help much. 
     62  * tried to move the filtering logic from outside endReadTrack() to inside TrackData guess what? As expected, it didn't help much also. 
     63  * tried messing with the listener attaching/detaching logic in AutoTracker.doUpdate(), and... it didn't help (: 
    6064 * I spotted lots of potential pieces of code which could possibly be optimized though this requires more time and analyzing and will be done in the next revision of this task. 
    61   * As mentioned, I tried several of them with not much luck. 
     65  * as mentioned, I tried several of them with not much luck. 
     66  * others need more thinking and useful profiler, so I'll try them in the next revision. 
    6267 
    6368Changeset: [2632]