* [sup-talk] Tuning Ruby's GC params for faster `sup`
@ 2014-06-13 0:04 Aravind Narayanan
2014-06-21 9:59 ` Ico Doornekamp
0 siblings, 1 reply; 3+ messages in thread
From: Aravind Narayanan @ 2014-06-13 0:04 UTC (permalink / raw)
To: sup-talk
[-- Attachment #1.1: Type: text/plain, Size: 711 bytes --]
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.
Anyone else notice this? Are there any other tricks people use to speed up
`sup`?
Regards,
Aravind
[-- Attachment #1.2: Type: text/html, Size: 973 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [sup-talk] Tuning Ruby's GC params for faster `sup`
2014-06-13 0:04 [sup-talk] Tuning Ruby's GC params for faster `sup` Aravind Narayanan
@ 2014-06-21 9:59 ` Ico Doornekamp
2014-06-21 17:55 ` Gaute Hope
0 siblings, 1 reply; 3+ messages in thread
From: Ico Doornekamp @ 2014-06-21 9:59 UTC (permalink / raw)
To: sup-talk
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.
Ico
--
:wq
^X^Cy^K^X^C^C^C^C
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [sup-talk] Tuning Ruby's GC params for faster `sup`
2014-06-21 9:59 ` Ico Doornekamp
@ 2014-06-21 17:55 ` Gaute Hope
0 siblings, 0 replies; 3+ messages in thread
From: Gaute Hope @ 2014-06-21 17:55 UTC (permalink / raw)
To: Ico Doornekamp; +Cc: sup-talk
[-- 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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-06-21 17:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-06-13 0:04 [sup-talk] Tuning Ruby's GC params for faster `sup` Aravind Narayanan
2014-06-21 9:59 ` Ico Doornekamp
2014-06-21 17:55 ` Gaute Hope
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox