If the required information for a eml-file is not found in the FileModel, the file is processed normaly and the info for this file is added to the FileModel. Information for no longer existing files are removed from the FileModel.
>2GB: this depends on the file count and MaxBytes (and some others) - it can be much more or much less. I expect 2GB for 30.000 files - a wild guess. My system requires ~ 1.2GB RAM for 20.000 files. >Does the new rebuildspam.pm improve rebuild time without enabling RebuildUsesFileModel? No. Thomas Von: "K Post" <nntp.p...@gmail.com> An: "ASSP development mailing list" <assp-test@lists.sourceforge.net> Datum: 09.11.2020 16:59 Betreff: Re: [Assp-test] fixes in assp 2.6.4 *SPAM-Evaporator* build 20310 Exciting changes. Thank you. On RebuildUsesFileModel, if ASSP crashes or the system is restarted, the RAM storage is obviously lost. Does the new process revert to the old method so that all messages from that day are considered during the rebuild? You gave 2gb as an example of additional memory for this new feature. What kind of email volume is that based on? Does the new rebuildspam.pm improve rebuild time without enabling RebuildUsesFileModel? Thanks again Ken On Thu, Nov 5, 2020 at 4:48 AM Thomas Eckardt <thomas.ecka...@thockar.com> wrote: H all, fixed in assp 2.6.4 *SPAM-Evaporator* build 20310: - trailing digits in the hostname (like 'mx.microsoft.com 1') in ARC-header lines were leading in to a 'notmatch' for trusted forwarder definitions changed: - The rebuildspamdb.pm module is upgraded to version 8.03. It provides faster rebuild processing, and much shorter locking times for HMMdb and SpamDB. - performance improvement for the import/export database feature - if email addresses and IP-addresses are managed using the GUI, a given reason and the date are written to the comment of the modified line - improved MIME-header fixup for missing boundary definitions - improved database cache handling added: 'RebuildUsesFileModel','Build a Model from all processed emails for faster processing' The rebuild task builds a content model (in memory or BerkelyDB only) of all processed files, and uses this model at the next rebuild for faster processing. The time to process the mail-files is reduced down to a tenth (if BerkeleyDB is not used ( useDB4Rebuild OFF )), but requires a large amount of additional memory - eg. 2GB. The time to process the mail-files is reduced to a half, if BerkeleyDB is used ( useDB4Rebuild ON ). The default setting is ON The first rebuild after setting this to ON will run at a normal speed - all the next rebuild tasks will run faster. Thomas DISCLAIMER: ******************************************************* This email and any files transmitted with it may be confidential, legally privileged and protected in law and are intended solely for the use of the individual to whom it is addressed. This email was multiple times scanned for viruses. There should be no known virus in this email! ******************************************************* _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test DISCLAIMER: ******************************************************* This email and any files transmitted with it may be confidential, legally privileged and protected in law and are intended solely for the use of the individual to whom it is addressed. This email was multiple times scanned for viruses. There should be no known virus in this email! *******************************************************
_______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
