unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Sam Saffron <sam.saffron@gmail.com>
Cc: unicorn-public@bogomips.org
Subject: Re: KGIO issues under WSL
Date: Tue, 14 Aug 2018 03:14:44 +0000	[thread overview]
Message-ID: <20180814031444.GA9808@dcvr> (raw)
In-Reply-To: <CAAtdryOtTO8HGTeKLy_JbeRhWLC7JZpCABVpbpEK+z67JHx=ew@mail.gmail.com>

Sam Saffron <sam.saffron@gmail.com> wrote:
> Howdy,
> 
> For some crazy reason we really want to run Unicorn on Windows
> Subsytem for Linux. We only use Unicorn in production and some of our
> devs like using WSL for "crazy reasons TM".
> 
> I guess the on-boarding is somewhat easier for Windows users vs
> spinning up a proper VM.

IMHO, you're holding your developers back and they'll constantly
be running into new problems in Ruby development.

> WSL overall works fine but is missing some socket options that mean
> Kgio is toast and you can not accept sockets.

WSL needs to add support for those Linux options if they intend
to pass themselves off as Linux-compatible.  And it seems you
guys pay for MS licenses, so they they should be fixing stuff
for you.

<snip>

> I was thinking since we are going to be giving up kgio longer term
> anyway, is there a way of having some flag for running unicorn without
> kgio or maybe even with minimal socket options given setsockoptions
> and getsockoptions are patchy. A monkey patch would be fine a well
> cause this is just for development and Puma seems to be ok-ish.

No flags or new options for this.  Ruby 2.3+ should be OK to run
entirely w/o kgio using the `exception: false` keyword.  I don't
know if you want to take a stab at it, there's not a whole lot
of kgio use in unicorn, even.

However, Ruby 2.0 and even 1.9.3 support should be maintained;
but maybe that can lazy-load kgio and fall back to expensive
exceptions if kgio isn't found.

There should be no increase in the bytecode or stack footprint
for 2.3+ users, but it's fine for users on older Rubies.

I also wouldn't worry about exception costs for exception paths
where kgio_trywrite tries to write something but gives up if it
doesn't work; but the accept_nonblock codepath is pretty critical
for being kept garbage-free.


Anyways, we will never advertise support for any proprietary
systems, if it works it's incidental.

(Abg gung jr nqiregvfr ng nyy :C)

      reply	other threads:[~2018-08-14  3:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-14  2:05 KGIO issues under WSL Sam Saffron
2018-08-14  3:14 ` Eric Wong [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://yhbt.net/unicorn/

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

  git send-email \
    --in-reply-to=20180814031444.GA9808@dcvr \
    --to=e@80x24.org \
    --cc=sam.saffron@gmail.com \
    --cc=unicorn-public@bogomips.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://yhbt.net/unicorn.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).