http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5141
------- Additional Comments From [EMAIL PROTECTED] 2006-11-27 19:44 ------- (In reply to comment #1) > temp files would be good. > > alternatives: > > - use RAM for the first N entries, then "page out" the remainder into temp > files > > - use a single delimiter-separated string in RAM; strings are much more > RAM-efficient than perl hashes or arrays yeah, I had a few thoughts about how to do it. the useful thoughts involved: - pass in function callbacks such that mass-check and spamassassin/sa-learn can function differently. for example, only mass-check cares about opt_n, after/before, etc. - if we're going to use temp files, we should generally be able to handle any amount of input. I'm worried about the performance penalty of doing everything in temp files, so yeah, churning through 50-100k entries in memory, then shove it out to a temp file. that way a small mass-check will still be all in memory, but larger ones will function appropriately. What I haven't figured out yet is the algorithm by which to handle the multiple message pools. It's pretty straightforward I think, though head and tail seems problematic. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
