Haha yeah, I've since changed my password and am using an encrypted command.
So I think I know why... I got throttled by Gmail. It suddenly got really fast about 30 minutes after I sent out my initial email... And it was really fast until I tried to sync my entire mailbox down to my other machine. As soon as I got the QUOTA error, it became really slow again. I'm going to check again during the day today to see if it speeds up again. Too bad Gmail doesn't give you a way to check your throttling status... On Thu, May 7, 2020, 01:23 Oswald Buddenhagen <oswald.buddenha...@gmx.de> wrote: > On Wed, May 06, 2020 at 02:30:22PM -0700, Howard Huang wrote: > >mbsync is working pretty well so far, but I have a question about > >performance. Every run of my `mbsync --all` takes over 3 minutes to fully > >complete. I'm sure I have something configured wrong, so I was wondering > if > >I can get any feedback of my configuration from you. > > > there is nothing obviously wrong with the config (it's just funny that > you echo a plaintext password instead of just using Pass instead). > re-run with the -DMn switch to see what it is spending time on. > if you simply have huge mailboxes, then doing a full sync each time > isn't the best idea and you might want to use --new instead. or the > MaxMessages option. > > > _______________________________________________ > isync-devel mailing list > isync-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/isync-devel >
_______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
