[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: rfc2047-decode-string in C?
From: |
Lars Magne Ingebrigtsen |
Subject: |
Re: rfc2047-decode-string in C? |
Date: |
Sat, 11 Sep 2010 18:10:52 +0200 |
User-agent: |
Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux) |
Lars Magne Ingebrigtsen <address@hidden> writes:
> Ok; I'll do some benchmarking over the weekend. (If I find the time
> after reimplementing nnimap.el.)
I've done some simple benchmarking by just disabling the
rfc2047-decoding in one Emacs and comparing group entry with decoding
versus group entry without decoding. (The assumption is that a
C-implemented rfc2047-decode-string would take zero time. :-)
I tried various groups, and selected 10K articles. Entry time was
between 5s and 10s with decoding. With the decoding disabled, group
entry was 15-20% faster.
--
(domestic pets only, the antidote for overdose, milk.)
address@hidden * Lars Magne Ingebrigtsen
- Re: Pushing the `gnus-range-*' functions down into the C layer, (continued)
Re: Pushing the `gnus-range-*' functions down into the C layer, Andy Wingo, 2010/09/10
Re: Pushing the `gnus-range-*' functions down into the C layer, Stefan Monnier, 2010/09/10
Re: Pushing the `gnus-range-*' functions down into the C layer, joakim, 2010/09/10
Re: Pushing the `gnus-range-*' functions down into the C layer, Lars Magne Ingebrigtsen, 2010/09/10
Re: Pushing the `gnus-range-*' functions down into the C layer, Stefan Monnier, 2010/09/10
Re: Pushing the `gnus-range-*' functions down into the C layer, Ted Zlatanov, 2010/09/10
Re: Pushing the `gnus-range-*' functions down into the C layer, Lars Magne Ingebrigtsen, 2010/09/10
Re: Pushing the `gnus-range-*' functions down into the C layer, Stefan Monnier, 2010/09/11
Re: Pushing the `gnus-range-*' functions down into the C layer, Lars Magne Ingebrigtsen, 2010/09/10
Re: Pushing the `gnus-range-*' functions down into the C layer, Daniel Pittman, 2010/09/10