From: Gaute Hope <eg@gaute.vetsj.com>
To: Ico Doornekamp <sup@zevv.nl>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Tuning Ruby's GC params for faster `sup`
Date: Sat, 21 Jun 2014 19:55:51 +0200 [thread overview]
Message-ID: <CABKe4MuExtbYOdiwUpx7hBeakQV+aW9pQ5LhxerfBHyECmx6uA@mail.gmail.com> (raw)
In-Reply-To: <1403344734-sup-985@pruts.nl>
[-- Attachment #1: Type: text/plain, Size: 1587 bytes --]
On Sat, Jun 21, 2014 at 11:59 AM, Ico Doornekamp <sup@zevv.nl> wrote:
> Hi,
>
> * On 2014-06-13 02:04:11 +0200, Aravind Narayanan wrote:
>
> > Hey everyone,
> >
> > I'm sharing this to see if any else does this, and whether or not it
> makes
> > sense to include in the defaults.
> >
> > `sup` was kind of slow for me, and sometimes took a few seconds to open
> up
> > an (albeit large) email thread. I ran `perftools.rb` on it to see what
> was
> > taking up so much time, and was surprised to find that ~ 60% of wallclock
> > time was spent in GC.
> >
> > So, I tuned Ruby's GC to not run so often, resulting in GC now taking
> only
> > 13% of wall clock time. Anecdotally, I also noticed that threads loaded
> > much much faster. The params I set were
> > https://gist.github.com/rvnd/756d6a5e82d1bba9fbb9.
>
> I can confirm this makes a *huge* difference. I'm running sup on a
> pretty big machine, but at times it's so creeping slow I'm considering
> moving back to mutt.
>
> Using the parameters you suggested speeds up things considerably,
> loading big threads is now fast enough to be usable without getting
> annoyed.
>
> Thank your *very* much for pointing this out. I hope Sup will pick this
> up and integrate it in the default application in some way.
>
Yup - that could be a possibility, would be happy to review a suggestion on
how to do it. This has always been a problem for Sup.
I would think either, a) suggest to the user to set the variables or b) set
them on start up (does ruby require them to be set beforehand? or is there
an interface to the GC?).
- gaute
[-- Attachment #2: Type: text/html, Size: 2234 bytes --]
prev parent reply other threads:[~2014-06-21 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 0:04 Aravind Narayanan
2014-06-21 9:59 ` Ico Doornekamp
2014-06-21 17:55 ` Gaute Hope [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=CABKe4MuExtbYOdiwUpx7hBeakQV+aW9pQ5LhxerfBHyECmx6uA@mail.gmail.com \
--to=eg@gaute.vetsj.com \
--cc=sup-talk@rubyforge.org \
--cc=sup@zevv.nl \
/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