From: James Rowe <jnrowe@gmail.com>
To: Eric Wong <e@80x24.org>
Cc: dtas-all@nongnu.org
Subject: Re: [PATCH 0/2] Trivial fixes for setup.rb usage.
Date: Mon, 2 Dec 2019 13:27:14 +0000 [thread overview]
Message-ID: <20191202132714.w45effcod74gbead@gmail.com> (raw)
In-Reply-To: <20191202082319.GA22184@dcvr>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
* Eric Wong (e@80x24.org) wrote:
> James Rowe <jnrowe@gmail.com> wrote:
> > Given that the `Config` name was removed so long ago, an alternative fix
> > might be to remove `setup.rb` altogether?
>
> RubyGems is a huge barrier to startup performance; so users
> should be able to opt-out of using gems. A painful thing is
> just having more gems installed (and even not using them)
> slows down startup.
Wow, I hadn’t realised how costly that was. As another data point for
your thoughts, my low-energy mobile Athlon reports:
▪ ~/P/dtas ψ:(master) ▶hyperfine --warmup 10 'dtas-ctl current'
Benchmark #1: dtas-ctl current
Time (mean ± σ): 236.0 ms ± 17.0 ms [User: 185.8 ms, System: 24.8 ms]
Range (min … max): 226.1 ms … 282.0 ms 11 runs
▪ ~/P/dtas ψ:(master) ▶hyperfine --warmup 10 'ruby --disable=g -Ilib ./bin/dtas-ctl current'
Benchmark #1: ruby --disable=g -Ilib ./bin/dtas-ctl current
Time (mean ± σ): 30.6 ms ± 6.3 ms [User: 21.1 ms, System: 4.6 ms]
Range (min … max): 27.0 ms … 63.9 ms 65 runs
On my system it makes little difference if you bypass gem’s script
wrapper unless you forcibly disable gems support like you suggest.
Thanks,
James
--
☒ Vote to destroy email signatures today!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-12-02 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 20:03 [PATCH 0/2] Trivial fixes for setup.rb usage James Rowe
2019-12-01 20:03 ` [PATCH 1/2] setup: update to use RbConfig James Rowe
2019-12-01 20:03 ` [PATCH 2/2] setup: fix duplicate variable warning James Rowe
2019-12-02 8:23 ` [PATCH 0/2] Trivial fixes for setup.rb usage Eric Wong
2019-12-02 13:27 ` James Rowe [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
List information: https://80x24.org/dtas/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191202132714.w45effcod74gbead@gmail.com \
--to=jnrowe@gmail.com \
--cc=dtas-all@nongnu.org \
--cc=e@80x24.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://80x24.org/dtas.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).