From: Ricardo Wurmus <rekado@elephly.net>
To: guile-email@systemreboot.net
Subject: [guile-email] slow parse of email with huge attachment
Date: Mon, 18 May 2020 00:06:06 +0200 [thread overview]
Message-ID: <87a726gqsx.fsf@elephly.net> (raw)
Hi,
bug 35518 contains an email with a 11+MB attachment. Viewing this in
the classic Debbugs web interface takes around 7 seconds:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35518
On mumi this times out. I benchmarked just the parsing step for all
emails in that bug log and I see around 0.1s used by my pre-processing
step (splitting the log at control characters) and around 8 seconds for
parse-email.
With all the slow, unoptimized post processing that I’m doing to render
things we hit around 14 seconds for this issue.
I wonder if parse-email could possibly be made even faster.
--
Ricardo
--
guile-email mailing list
guile-email@systemreboot.net
https://lists.systemreboot.net/listinfo/guile-email
next reply other threads:[~2020-05-18 0:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 22:06 Ricardo Wurmus [this message]
2020-05-18 1:13 ` Arun Isaac
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=87a726gqsx.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guile-email@systemreboot.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