Ticket #839 (closed: fixed)
Automatic install and execution of performance tests
Reported by: | Nick Draper | Owned by: | Janik Zikovsky |
---|---|---|---|
Priority: | critical | Milestone: | Iteration 30 |
Component: | Tools | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Russell Taylor |
Description (last modified by Nick Draper) (diff)
This can use the same approach as the system tests for automatic install of the msi (for windows at least).
We could even chain the two together such that we do a fresh install once and then run the system tests and the performance tests. We should still report them both out seperately.
It may be good idea to make both types of tests record the results in an xml file that Jenkins can read.
This may remove the need to track the history of the performance tests ourselves so much, and give us a way of plotting trends.
However we do need a reasonable way of defining what a significant change in performance is. One possibility would be that in the test you specify an accepted variance (default 10%), and that each run would be compared to the average of the last 5 days runs (on this environment), if it varies by more than the acceptable variance then the test should fail. Of course that means you will need to keep track of the last 5 days of runs of the test, perhaps a simple text file would do.
Change History
comment:3 Changed 11 years ago by Nick Draper
- Status changed from new to assigned
- Owner changed from Martyn Gigg to Russell Taylor
comment:5 Changed 10 years ago by Nick Draper
- Milestone changed from Iteration 26 to Iteration 27
Bulk move of tickets to iteration 27, if your ticket is essential for Iteration 26 then move it back.
comment:6 Changed 10 years ago by Nick Draper
- Milestone changed from Iteration 27 to Iteration 28
Bulk move of tickets at the end of iteration 27
comment:7 Changed 10 years ago by Nick Draper
- Owner changed from Russell Taylor to Janik Zikovsky
- Priority changed from minor to critical
- Component set to Tools
- Description modified (diff)
- Summary changed from Automatic install and execution of stress tests to Automatic install and execution of performance tests
comment:10 Changed 10 years ago by Janik Zikovsky
comment:11 Changed 10 years ago by Janik Zikovsky
comment:12 Changed 10 years ago by Janik Zikovsky
comment:13 Changed 10 years ago by Janik Zikovsky
comment:14 Changed 10 years ago by Janik Zikovsky
comment:15 Changed 10 years ago by Janik Zikovsky
comment:16 Changed 10 years ago by Janik Zikovsky
comment:17 Changed 10 years ago by Janik Zikovsky
comment:18 Changed 10 years ago by Janik Zikovsky
comment:19 Changed 10 years ago by Janik Zikovsky
comment:20 Changed 10 years ago by Janik Zikovsky
comment:21 Changed 10 years ago by Janik Zikovsky
comment:22 Changed 10 years ago by Janik Zikovsky
comment:23 Changed 10 years ago by Janik Zikovsky
comment:24 Changed 10 years ago by Janik Zikovsky
comment:25 Changed 10 years ago by Janik Zikovsky
comment:26 Changed 10 years ago by Janik Zikovsky
comment:27 Changed 10 years ago by Janik Zikovsky
comment:28 Changed 10 years ago by Janik Zikovsky
comment:29 Changed 10 years ago by Janik Zikovsky
comment:30 Changed 10 years ago by Janik Zikovsky
comment:31 Changed 10 years ago by Janik Zikovsky
comment:32 Changed 10 years ago by Janik Zikovsky
comment:33 Changed 10 years ago by Janik Zikovsky
comment:34 Changed 10 years ago by Janik Zikovsky
comment:35 Changed 10 years ago by Janik Zikovsky
comment:36 Changed 10 years ago by Janik Zikovsky
comment:37 Changed 10 years ago by Janik Zikovsky
comment:38 Changed 10 years ago by Janik Zikovsky
comment:39 Changed 10 years ago by Janik Zikovsky
comment:40 Changed 10 years ago by Janik Zikovsky
comment:41 Changed 10 years ago by Janik Zikovsky
comment:42 Changed 10 years ago by Janik Zikovsky
comment:43 Changed 10 years ago by Janik Zikovsky
comment:44 Changed 10 years ago by Janik Zikovsky
comment:45 Changed 10 years ago by Janik Zikovsky
comment:46 Changed 10 years ago by Janik Zikovsky
comment:47 Changed 10 years ago by Janik Zikovsky
comment:48 Changed 10 years ago by Janik Zikovsky
comment:49 Changed 10 years ago by Janik Zikovsky
comment:50 Changed 10 years ago by Janik Zikovsky
comment:51 Changed 10 years ago by Janik Zikovsky
comment:52 Changed 10 years ago by Janik Zikovsky
comment:53 Changed 10 years ago by Janik Zikovsky
comment:54 Changed 10 years ago by Janik Zikovsky
comment:55 Changed 10 years ago by Janik Zikovsky
comment:56 Changed 10 years ago by Janik Zikovsky
comment:57 Changed 10 years ago by Janik Zikovsky
comment:58 Changed 10 years ago by Janik Zikovsky
comment:59 Changed 10 years ago by Janik Zikovsky
comment:60 Changed 10 years ago by Janik Zikovsky
comment:61 Changed 9 years ago by Janik Zikovsky
- Milestone changed from Iteration 28 to Iteration 29
comment:62 Changed 9 years ago by Janik Zikovsky
comment:63 Changed 9 years ago by Janik Zikovsky
comment:64 Changed 9 years ago by Janik Zikovsky
comment:65 Changed 9 years ago by Janik Zikovsky
comment:66 Changed 9 years ago by Janik Zikovsky
- Milestone changed from Iteration 29 to Iteration 30
Moved my tickets that won't get finished by iteration 29
comment:67 Changed 9 years ago by Janik Zikovsky
comment:68 Changed 9 years ago by Janik Zikovsky
In [13237]:
comment:69 Changed 9 years ago by Janik Zikovsky
- Status changed from accepted to verify
- Resolution set to fixed
OK, this ticket has been pretty much fixed for ages, and the performance tests are running on a regular basis. Time for fresh tickets instead of always using this one.
Fixed!
comment:70 Changed 9 years ago by Janik Zikovsky
In [13707]:
comment:71 Changed 9 years ago by Russell Taylor
- Status changed from verify to verifying
- Tester set to Russell Taylor
comment:72 Changed 9 years ago by Russell Taylor
- Status changed from verifying to closed
We have performance testing in production via the ORNL Jenkins! It doesn't work quite as set out in the ticket description, in that it is integrated into cxxtest/ctest rather than running off an installed version. We have it running on rhel, but there's no reason why it shouldn't work anywhere. The automatic emails are almost always spurious (maybe we should up the threshold), but the plots accessible via Jenkins mean it's easy to periodically scan all the test results and spot slowdowns.
Now we need more performance tests!
comment:73 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 1687
Moved as part of the end of Iteration 19