-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
afew is very slow #243
Comments
Hello, Joke aside, to help you we need more informations, I have a nearly 900k mail in my boxes and it works fine |
Same here. Even when there is no new mail, afew takes some seconds to process for me. |
|
Hello @DearRude, No new mail so nothing to do for notmuch 0.01s Then each line in afew is doing a real query and adding some tag, and ~10s of afew run is not so slow if you consider how much stuff it does (it could be faster of course). If you want to compare, you need to get a single process like:
Add a more verbose output to get the actual query, run each changes manually + time, |
Is it necessary for |
Probably as afew is not the database itself, it has to rely on notmuch to return the list, |
As listed in the verbose output, |
Hey @DearRude , [new]
tags=new
... So if you use the --new option it will only target those new mail, if you increase the verbose level more, I was trying to say before, afew may be slow but you have to compare it to all the queries / changes it does. |
Ah got it. Thank you! |
Hey @GuillaumeSeren What I mean is that |
For some reason afew is taking a very long time (like a half hour or more) to process mail. Admittedly there are many mails (hundreds of thousands) but afew sits at the "Commit changes to N messages" for long periods.
Even when only processing new mail, afew takes much longer than I would expect.
The text was updated successfully, but these errors were encountered: