|
We went through the process of changing from a V2 BDB to a
V3 DBD then -> MySQL. When running the tests side by side, old system with new we
see some substantial inconsistencies between the bayes scoring… Any ideas why ? There are obviously fewer tokens now
than before the sync, but no mention in the docs of data being lost… Thanks Michael Grey Old System’s bdb info : 0.000
0
2 0 non-token data:
bayes db version 0.000
0
3541311 0 non-token
data: nspam 0.000
0
1707362 0 non-token
data: nham 0.000
0
343897 0 non-token
data: ntokens 0.000
0 1157674321 0
non-token data: oldest atime 0.000
0 1157749228 0
non-token data: newest atime 0.000
0 1157749183 0
non-token data: last journal sync atime 0.000
0 1157717569 0
non-token data: last expiry atime 0.000
0
43200 0 non-token
data: last expire atime delta 0.000
0
145970 0 non-token
data: last expire reduction count New systems bdb info after –sync : 0.000
0
3 0 non-token data:
bayes db version 0.000
0
3541670 0 non-token
data: nspam 0.000
0
1707603 0 non-token
data: nham 0.000
0
263855 0 non-token
data: ntokens 0.000
0 1157707085 0
non-token data: oldest atime 0.000
0 1157755124 0
non-token data: newest atime 0.000
0
0 0 non-token data:
last journal sync atime 0.000
0
0 0 non-token data:
last expiry atime 0.000
0
0 0 non-token data:
last expire atime delta 0.000
0
0 0 non-token data:
last expire reduction count |
