From: Andreas Politz <politza@hochschule-trier.de>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: 14776@debbugs.gnu.org
Subject: bug#14776: 24.3.50; [PATCH] parse-time-string performance
Date: Thu, 04 Jul 2013 23:08:33 +0200 [thread overview]
Message-ID: <87ppuyhw32.fsf@hochschule-trier.de> (raw)
In-Reply-To: <m3y59mrrrs.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 04 Jul 2013 22:31:35 +0200")
[-- Attachment #1: Type: text/plain, Size: 242 bytes --]
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> It's not much of a bottleneck, no:
>
> (benchmark-elapse (dotimes (i 10000) (parse-time-string "Thu, 04 Jul 2013 20:06:00 +0200")))
> => 1.120856647
=> 0.215108395
;-O
But only with this:
[-- Attachment #2: parse-time-rfc2822.el --]
[-- Type: application/emacs-lisp, Size: 2006 bytes --]
[-- Attachment #3: Type: text/plain, Size: 490 bytes --]
> But sorting a summary buffer of 5K messages on Date (which some people
> do) might get a performance boost. But I was thinking that it might be
> more likely that parse-datetime parses more date strings correctly than
> the version in parse-time.el.
It looks that way, i.e. parse-time-string is pretty simple compared to
that. But most Date header I've seen popping up in my mail seem to
adhere to a strict rfc2822 format anyway, except for the occasional
non-strict timezone.
-ap
next prev parent reply other threads:[~2013-07-04 21:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 1:21 bug#14776: 24.3.50; [PATCH] parse-time-string performance Andreas Politz
2013-07-03 1:27 ` Andreas Politz
2013-07-03 3:32 ` Glenn Morris
2013-07-03 3:34 ` Glenn Morris
2013-07-04 15:41 ` Andreas Politz
2013-07-04 18:41 ` Lars Magne Ingebrigtsen
2013-07-04 19:47 ` Andreas Politz
2013-07-04 20:31 ` Lars Magne Ingebrigtsen
2013-07-04 21:08 ` Andreas Politz [this message]
2013-07-04 21:15 ` Lars Magne Ingebrigtsen
[not found] ` <87hagaeztj.fsf@hochschule-trier.de>
2013-07-06 15:34 ` Lars Ingebrigtsen
2013-07-06 15:50 ` Andreas Politz
2013-07-06 15:56 ` Lars Ingebrigtsen
2013-07-06 16:07 ` Andreas Politz
2013-07-06 17:47 ` Andreas Politz
2013-07-08 14:51 ` Lars Magne Ingebrigtsen
2016-03-01 1:05 ` Lars Ingebrigtsen
2019-06-27 11:12 ` Lars Ingebrigtsen
2013-07-04 22:21 ` Andreas Politz
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ppuyhw32.fsf@hochschule-trier.de \
--to=politza@hochschule-trier.de \
--cc=14776@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).