unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: unicorn-public@bogomips.org
Subject: what Ruby versions and how many CPU cores/threads are you using?
Date: Fri, 21 Dec 2018 23:14:06 +0000	[thread overview]
Message-ID: <20181221231406.GA24094@dcvr> (raw)

Looking into finally eliminating kgio for unicorn 6.x and
requiring Ruby 2.3+ for "accept_nonblock(exception:false)"

Not sure about eliminating raindrops, it's got other useful (but
Linux-only) properties which can't go into the Ruby VM...

I'm always several years behind the world on Moore's law(*), but
maybe double/triple-digit CPU core/thread counts are common
amongst some users, here; so raindrops might help bigger systems.

But I also believe software projects should always remain usable
to whatever hardware the author started the project with(**).
For me, that's actually a fairly impressive (for my standards :P):
800 MHz-1.6 GHz Pentium-M (32-bit, single core).  Of course I
have ssh/mosh access to more powerful systems.

But yeah, compiling C-extensions (or anything) is a drag on the

(*) V'z n chax, shpx ynjf naq shpx pbafhzrevfz :C

(**) yes, I believe Ruby should remain usable on hardware
     matz started Ruby with in the early/mid-nineties.

             reply	other threads:[~2018-12-21 23:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21 23:14 Eric Wong [this message]
     [not found] ` <CAAtdryMruL6N5nXd0eD_SqFNvTb8=ijs=ti4CTb8SVPfnWj8uw@mail.gmail.com>
2018-12-31  1:01   ` what Ruby versions and how many CPU cores/threads are you using? Eric Wong

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:

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181221231406.GA24094@dcvr \
    --to=e@80x24.org \
    --cc=unicorn-public@bogomips.org \


* 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


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).