https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8346

            Bug ID: 8346
           Summary: Bayestest extremely slow since 4.0.2
           Product: Spamassassin
           Version: 4.0.2
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Regression Tests
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: Undefined

The t/bayes*.t tests would finish quickly in 4.0.1:

[   74s] t/bayesbdb.t ...................... skipped: BerkeleyDB is unavailable
[   82s] t/bayesdbm.t ...................... ok
[   89s] t/bayesdbm_flock.t ................ ok
[   96s] t/bayessdbm.t ..................... ok
[  102s] t/bayessdbm_seen_delete.t ......... ok

But with 4.0.2 the run times have gone *way* up:

[  213s] t/bayesbdb.t ...................... skipped: BerkeleyDB is unavailable
[ 2670s] t/bayesdbm.t ...................... ok
[ 4919s] t/bayesdbm_flock.t ................ ok
[ 7166s] t/bayessdbm.t ..................... ok
[ 9414s] t/bayessdbm_seen_delete.t ......... ok

The problem is not only in these tests, it also takes almost three times as
long to reach the first one. Environment is the same in both cases (Perl 5.42).

My concern is that whatever causes to slow these regression tests, will also
wreak havoc on the performance of spamassassin in a production system.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to