Anton Khirnov <[email protected]> writes: > Quoting David Bremner (2026-04-04 09:57:29) >> Anton Khirnov <[email protected]> writes: >> >> > --- >> > test/T681-index-filter.sh | 84 +++++++++++++++++++++++++++++++++++++++ >> > 1 file changed, 84 insertions(+) >> > create mode 100755 test/T681-index-filter.sh >> > >> >> BTW, I think we talked about performance tests for the filtering at some >> point. I just checked, and the enron corpus has some >> attachements. There are about 6600 word documents and about 3500 excell >> documents. I guess we probably should not trust those attachments. > > The question is, are measuring performance of just the libnotmuch > interface, or of the whole package including the sample filter.py, > whatever programs it invokes, and the sandbox?
We chatted about this briefly on IRC. To summarize my comments from then, 1) Existing performance tests are enough for making sure the theoretically negligible performance impact for people not using the new feature really is negligible. 2) It seems likely that users will have performance problems to debg with this new feature, and it would be helpful to have some kind of baseline test so that we can establish that some trivial filtering is within expected an performance on their machine. This will also help guard against performance regressions in attachment indexing introduced by other changes to libnotmuch. I don't think we really discussed how much effort was involved with implementing (and I guess maintaining) such a test, since we didn't really get past motivation(s) for doing so. d _______________________________________________ notmuch mailing list -- [email protected] To unsubscribe send an email to [email protected]
