From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Asynchronous NNTP group data fetching
Date: Mon, 31 Jan 2011 17:21:08 -0800 [thread overview]
Message-ID: <87aaigmtx7.fsf@gnus.org> (raw)
In-Reply-To: <87vd15f3ql.fsf@dod.no>
Steinar Bang <sb@dod.no> writes:
> So... it's nearly twice as fast in real time used,
Yay!
> but it spends more time in garbage collection.
Boo.
Actually, I'm somewhat surprised that is generates significantly more
garbage. I've looked over the code, and it seems, if anything, slightly
less consing than before...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2011-02-01 1:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 3:18 Lars Ingebrigtsen
2011-01-31 16:16 ` Steinar Bang
2011-02-01 1:21 ` Lars Ingebrigtsen [this message]
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=87aaigmtx7.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=ding@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.
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 NNTP newsgroup(s).