Changes between Version 10 and Version 11 of PRO_LIB_CORE_PERFORMANCE_R0


Ignore:
Timestamp:
01/28/09 15:57:00 (16 years ago)
Author:
gogov
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PRO_LIB_CORE_PERFORMANCE_R0

    v10 v11  
    33[[TicketQuery(summary=PRO_LIB_CORE_PERFORMANCE_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]] 
    44 
    5  
    6  
    75= Analysis = 
    86== Overview == 
    9 The aim of this task is to research and to improve efficiency of the library "org.sophie2.core.prolib".  
     7The goal of this task is to develop a strategy for dealing with performance issues in the ProLib. [[BR]] 
     8The focus in this task is on performance measured in time. There's a separate task for memory management and optimizations. 
    109 
    1110== Task requirements == 
    12  
    13       1. Research the library for bottle necks.[[BR]] 
    14       2. Improve the efficiency of the library. [[BR]] 
    15       EXTRA [[BR]] 
    16       3. Make new tests.[[BR]] 
    17       4. Write a document, in which is written an analysis of the research for bottle necks  
    18          and the idea for their improvements. 
     11 * Devise an overall concept how to measure performance: 
     12  * what is to have its performance measured? 
     13   * performance tests, written for specific measurements 
     14   * unit tests 
     15   * other? 
     16  * how to measure it? 
     17   * by a self-written utility, which will be developed by our team, or 
     18   * some kind of a profiler [[BR]] 
     19  Argue on the two possibilities and provide details on the self-written utility or propose concrete profiler to use. 
     20  * how to identify and deal with bottlenecks 
     21  * generating performance reports 
     22   * what to include in the reports 
     23   * how often to generate them 
     24   * where to upload them 
     25   * how to generate them 
     26    * with some sort of script? 
     27    * can these reports be integrated with Maven 
     28  * how to identify performance regressions 
     29  * where and how to apply algorithmic optimizations 
     30 * According to this concept locate concrete problems and propose solutions to them 
     31 * Write appropriate tests for these problems 
    1932 
    2033== Task result == 
    21 The result of this task should be source code. Optional - new tests and a document. 
     34 * Description of the developed concept in this wiki page 
     35 * List of concrete problems and solutions 
     36 * Possibly new code which fixes located problems 
     37 * Possibly new tests which correspond the located problems 
    2238 
    2339== Implementation idea == 
    24 There is two way to do the task. First way is algorithmic. Search the places with bad efficiency and replace it with another new algorithms with better efficiency. The second way is empiric, e.g. the library is measured, bottle necks are found,  and optimisations are made. All tests are working in module "org.sophie2.core.prolib". You can use it, but it is recommended to make new tests,too. Write a document, in which is written an analysis of the research for bottle necks in the library .The document has to contain the idea for the improvements of bottle necks ,too. 
     40 * Look for a suitable profiler in the JDK 
     41 
    2542== Related == 
    2643[wiki:PRO_LIB_CORE_MEMORY_MANAGEMENT_R0][[BR]] 
    27  
    2844[wiki:PLATFORM_NFR_EFFIECENCY_R0] 
    2945 
    3046== How to demo == 
    31 Show the results before and after the improvements.A document with needed information. 
     47 * Explain the developed concept 
     48 * Explain the problems and proposed solutions 
     49 * Run the newly created unit tests, if any 
    3250 
    3351= Design =