Bug #58745 | MTR spends long time checking for warnings | ||
---|---|---|---|
Submitted: | 5 Dec 2010 22:56 | Modified: | 2 May 2011 14:56 |
Reporter: | Elena Stepanova | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Tools: MTR / mysql-test-run | Severity: | S5 (Performance) |
Version: | 5.5.8 | OS: | Any |
Assigned to: | Bjørn Munch | CPU Architecture: | Any |
[5 Dec 2010 22:56]
Elena Stepanova
[6 Dec 2010 9:20]
Bjørn Munch
Some speedup may be possible, but it's implemented in a way which is not very optimal, doing the matching against suppressed patterns in SQL. I'm not sure it will be more optimal in Perl though; the number of comparisons needed is number of warnings x number of suppress patterns. A workaround for a specific test could be to add --testcase-timeout=60 to <test>-master.opt; this will increase the check warnings timeout to 1/10 of that, or 6 minutes. Adjust according to your needs.
[2 May 2011 14:56]
Paul DuBois
Changes to test suite. No changelog entry needed.