On 1/3/07, Gary V <[EMAIL PROTECTED]> wrote:
>It finally finished the restore.
>
>For the sake of information to help future users....
>
>The "backup" file being used to restore into the new SQL database was
>99MB and took 17hrs to import on my AMD 1.2Ghz machine with 1GB of
>RAM.
>
>Dave
Could be your database was not expiring. Probably a good idea to do a
--force-expire prior to a backup. Just curious, If you run --force-expire
now, what does --dump magic look like?
Gary V
Here are the numbers...
[EMAIL PROTECTED] ~]# sa-learn --dump magic
0.000 0 3 0 non-token data: bayes db version
0.000 0 253 0 non-token data: nspam
0.000 0 580 0 non-token data: nham
0.000 0 3637103 0 non-token data: ntokens
0.000 0 1167206400 0 non-token data: oldest atime
0.000 0 1167890964 0 non-token data: newest atime
0.000 0 0 0 non-token data: last journal sync atime
0.000 0 1167891012 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
[EMAIL PROTECTED] ~]# sa-learn --force-expire
[EMAIL PROTECTED] ~]# sa-learn --dump magic
0.000 0 3 0 non-token data: bayes db version
0.000 0 253 0 non-token data: nspam
0.000 0 580 0 non-token data: nham
0.000 0 3637103 0 non-token data: ntokens
0.000 0 1167206400 0 non-token data: oldest atime
0.000 0 1167890964 0 non-token data: newest atime
0.000 0 0 0 non-token data: last journal sync atime
0.000 0 1167891646 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
[EMAIL PROTECTED] ~]#
It would appear to me as if it hasn't changed the number of tokens at all.
Dave
