History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: COR-1134
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Adriano Verona
Reporter: Rodrigo B. de Oliveira
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
db4o Core

Poleposition alerts when the performance decreases or increases by a specific threshold

Created: 04/Feb/08 05:10 PM   Updated: 15/Dec/09 02:22 PM
Return to search
Component/s: None
Affects Version/s: None
Fix Version/s: 7.10.104

Time Tracking:
Original Estimate: Not Specified
Remaining Estimate: Not Specified
Time Spent - 9.52h
Time Spent: 9.52h
Time Spent - 9.52h

File Attachments: None
Image Attachments:

1. Output.jpeg
(24 kb)

Peers: Patrick Roemer
Order: 2
Iteration: 104
Original IDS Estimate: 2
Resolution Date: 21/Jul/09 01:16 PM
First Response Date: 13/Feb/08 10:25 AM
Labels:
Participants: Adriano Verona, Patrick Roemer and Rodrigo B. de Oliveira
Number of Attachments: 1
Number of Comments: 4


 Description  « Hide
The continuous poleposition run should send email alerts when it's detected that the performance dropped or increased by a specific threshold against the last release or against the last run (every run could simply keep a file with the last results and compare).

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Change by Richard Liang - 12/Feb/08 03:49 PM
Field Original Value New Value
Peers [richard_liang]

Change by Adriano Verona - 12/Feb/08 03:51 PM
Assignee Adriano Verona [ adriano verona ]

Change by Adriano Verona - 12/Feb/08 08:02 PM
Attachment Output.jpeg [ 10587 ]

Change by Adriano Verona - 12/Feb/08 08:07 PM
Comment [ Possible approaches:

1) Enhance Polepos:
      - Change Racer#run() to post check the results

2) Post process the results

Personally I think 1 would be a better solution (and easier to implement also).


-------------------------
Required configurations:

- Threshold (in percentage) (applies to all Circuits/Laps)

- Notification list

- Email
     - Subject
     - Sender email
     - SMTP server to use

--------------
Possible output (attached file)

Green: Performance increase
Yellow: Some performance indicators were better, some worst.
Red: Performance decrease


--------------
Questions

- Which teams should be took into account? I guess the last 2 teams.

]

Change by Adriano Verona - 13/Feb/08 10:18 AM
Comment [ Possible approaches:

1) Enhance Polepos:
      - Change Racer#run() to post check the results
      - Always include trunk in the teams

2) Post process the results

Personally I think 1 would be a better solution (and easier to implement also).


-------------------------
Required configurations:

- Threshold (in percentage) (applies to all Circuits/Laps)

- Notification list

- Email
     - Subject
     - Sender email
     - SMTP server to use

--------------
Possible output (attached file)

Green: Performance increase
Yellow: Some performance indicators were better, some worst.
Red: Performance decrease


--------------
Questions

- Which teams should be took into account? I guess the last 2 teams.
-
]

Change by Adriano Verona - 13/Feb/08 10:26 AM
Comment [ Possible approaches:

1) Enhance Polepos:
      - Change Racer#run() to check the results
- Pass a parameter with the names of the teams to track performance for
      - Always include trunk in the teams

1.1) Load configuration
1.2) Figure out db4o trunk version and pass this to AbstractDb4oVersionsRaceRunner (will be used in #run method)
1.3) Collect actual performance information for desired teams
1.4) Check for performance variation
1.4.1) Check if there's previous performance information (file)
1.4.2) If not, just save the current performance info (no email)
1.4.3) Compare performance information and save the new performance data.
1.4.4) Send an email

2) Post process the results (separete program run after polepos in cc)
2.1) Load configuration
2.2) Collect performance data
2.2.1) Scan for files like *.f1graph in doc/results
2.2.2) Create an object to agregate performance information for the target team
2.2.3) Load previous agregated performance information file
2.2.4) If the file doesn't exist, save the just collected data
2.2.5) Compare performance information and save the new performance data.
2.2.6) Send an email.

Personally I think 1 would be a better solution (and easier to implement also).


-------------------------
Required configurations:

- Threshold (in percentage) (applies to all Circuits/Laps)

- Notification list

- Email
     - Subject
     - Sender email
     - SMTP server to use

--------------
Possible output (attached file)

Green: Performance increase
Yellow: Some performance indicators were better, some worst.
Red: Performance decrease


--------------
Questions

- Which teams should be took into account? I guess the last 2 teams.
- ]

Change by Adriano Verona - 13/Feb/08 12:12 PM
Original IDS Estimate 2

Change by Adriano Verona - 13/Feb/08 02:42 PM
Iteration 30

Change by Adriano Verona - 13/Feb/08 03:15 PM
Original IDS Estimate 2 4

Change by Adriano Verona - 13/Feb/08 03:42 PM
Iteration 30

Change by Carl Rosenberger - 19/Feb/08 01:52 PM
Order 3 7

Change by Adriano Verona - 26/Feb/08 12:13 PM
Peers [richard_liang]
Assignee Adriano Verona [ adriano verona ]

Change by Carl Rosenberger - 10/Feb/09 01:57 PM
Order 8

Change by Rodrigo B. de Oliveira - 13/Jul/09 04:15 PM
Order 8 2

Change by Adriano Verona - 14/Jul/09 03:09 PM
Link This issue is related to INF-10 [ INF-10 ]

Change by Adriano Verona - 14/Jul/09 04:06 PM
Assignee Adriano Verona [ adriano verona ]
Iteration 104
Peers [patrick roemer]

Change by Adriano Verona - 15/Jul/09 02:17 PM
Original IDS Estimate 4

Change by Patrick Roemer - 15/Jul/09 03:13 PM
Original IDS Estimate 2

Change by Patrick Roemer - 21/Jul/09 01:16 PM
Status Open [ 1 ] Resolved [ 5 ]
Fix Version/s 7.10.104 [ 10560 ]
Resolution Fixed [ 1 ]

Change by Adriano Verona - 21/Jul/09 01:29 PM
Time Spent 2.52h [ 9060 ]

Change by Adriano Verona - 21/Jul/09 01:29 PM
Time Spent 2.52h [ 9060 ] 6.52h [ 23460 ]

Change by Adriano Verona - 21/Jul/09 01:29 PM
Time Spent 6.52h [ 23460 ] 9.52h [ 34260 ]

Change by Adriano Verona - 15/Dec/09 02:22 PM
Status Resolved [ 5 ] Closed [ 6 ]