Changes between Version 3 and Version 4 of PLATFORM_NFR_EFFIECENCY_R1


Ignore:
Timestamp:
12/29/08 14:43:29 (16 years ago)
Author:
deyan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PLATFORM_NFR_EFFIECENCY_R1

    v3 v4  
    66 
    77= Analysis = 
     8== Overview == 
    89[wiki:PLATFORM_NFR_EFFICIENCY] should collect useful statistics on resources usage in Sophie 2. As memory and CPU usage is important aspect for the project, efficiency should help developers to see different module performance. 
    9 == Overview == 
    10 ^(The analysis of the first revision of each task should contain a brief overview of the whole task. Stick to the current revision of the task, but keep an eye to the whole task progress, and stay alert for possible smells.)^ 
    1110 
    1211== Task requirements == 
    13 ^(Necessary requirements that the task must fulfill.)^ 
    14  
     12 * Correct misspelled word EFFIECENCY (should be EFFIECIENCY) where needed. 
     13 * Research for better performace benchmark solution - currently a trial plugin is used 
     14 * Setup chosen tool and perform efficiency tests 
     15 * Define a schedule for running the tests 
     16 * Define where the results should be stored 
     17 * See implementation idea for example tools 
     18 * Make sure that the requirements from [wiki:PLATFORM_NFR_EFFIECENCY_R0] are satisfied! 
    1519== Task result == 
    16 ^(The Analysis should contain strict requirements about the end product of the task (for example the result must be source code, the result must be google doc, etc.))^ 
     20wiki page, maintained wiki pages 
    1721 
    1822== Implementation idea == 
    19 ^(It is advisable to include some rough implementations ideas.)^ 
     23http://clif.objectweb.org/ CLIF looks promising and seems to satisfy the demands. 
     24{{{ 
     25CLIF is a modular and flexible distributed load testing platform. It may address any target system that is reachable from a Java program (HTTP, DNS, TCP/IP...) CLIF provides 3 user interfaces (Swing or Eclipse GUI, command line) to deploy, control and monitor a set of distributed load injectors and resource consumption probes (CPU, memory...) An Eclipse wizard helps programming support for new protocols. Load scenarios are defined through XML-editing, using a GUI, or using a capture tool. The scenario execution engine allows the execution of up to millions of virtual users per load injector. 
     26}}} 
     27== Related == 
     28http://clif.objectweb.org/doc/user_manual/CLIFTutorial.pdf 
     29http://www.opensourcetesting.org/performance.php 
    2030 
    21 == Related == 
    22 ^(Here you can add related tasks that could be useful or helpful.)^ 
    2331 
    2432== How to demo ==