From: Arun Isaac <arunisaac@systemreboot.net>
To: Ricardo Wurmus <rekado@elephly.net>, guile-email@systemreboot.net
Subject: Re: [guile-email] slow parse of email with huge attachment
Date: Mon, 18 May 2020 06:43:18 +0530 [thread overview]
Message-ID: <cu7wo5aniz5.fsf@systemreboot.net> (raw)
Message-ID: <20200518011318.Z1qsfIE-NreTzHS5QGCrK1jJ2-rlJYhuZqeH3x0Cin8@z> (raw)
In-Reply-To: <87a726gqsx.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
Hi,
Yes, guile-email is quite slow. I think it is because it does multiple
passes of each email trying to split MIME entities and what not. For a
long time, I've been meaning to rewrite guile-email to only do a single
pass. It's quite a bit of work, but I'll try to finish it in a week.
Meanwhile, if you have any benchmarking scripts, do share those. It
would help me get a head start on the problem.
Thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-05-18 1:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 22:06 Ricardo Wurmus
2020-05-18 1:13 ` Arun Isaac [this message]
2020-05-18 1:13 ` Arun Isaac
2020-05-18 20:50 ` Ricardo Wurmus
2020-05-19 2:33 ` Arun Isaac
2020-05-19 2:33 ` Arun Isaac
2020-05-25 14:52 ` Arun Isaac
2020-05-25 14:52 ` Arun Isaac
2020-05-25 15:08 ` Arun Isaac
2020-05-25 15:08 ` Arun Isaac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cu7wo5aniz5.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=guile-email@systemreboot.net \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox