* what Ruby versions and how many CPU cores/threads are you using?
@ 2018-12-21 23:14 Eric Wong
[not found] ` <CAAtdryMruL6N5nXd0eD_SqFNvTb8=ijs=ti4CTb8SVPfnWj8uw@mail.gmail.com>
0 siblings, 1 reply; 2+ messages in thread
From: Eric Wong @ 2018-12-21 23:14 UTC (permalink / raw)
To: unicorn-public
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
Pentium-M...
(*) 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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: what Ruby versions and how many CPU cores/threads are you using?
[not found] ` <CAAtdryMruL6N5nXd0eD_SqFNvTb8=ijs=ti4CTb8SVPfnWj8uw@mail.gmail.com>
@ 2018-12-31 1:01 ` Eric Wong
0 siblings, 0 replies; 2+ messages in thread
From: Eric Wong @ 2018-12-31 1:01 UTC (permalink / raw)
To: Sam Saffron; +Cc: unicorn-public, raindrops-public
Sam Saffron <sam.saffron@gmail.com> wrote:
> Quick data point from Discourse. We use raindrops quite a lot for basic
> graphing of processing/queued connection counts. Shifting to Ruby 2.3+
> would pose no problem to us, we already deploy our main application on 2.5.
>
> With raindrops we use it for graphing queued and active web requests,
> this is quite
> important for us as we are heavy consumers of rack hijack, so almost always have
> more requests going than count of active unicorn workers.
Thanks for the info. Unfortunately it contained an image so it
couldn't be archived; so I'm quoting your text in full.
> [-- Attachment #2: requests.PNG --]
> [-- Type: image/png, Encoding: base64, Size: 65K --]
I can't afford to support images (the software can, but the
human and hardware cost is too high for a decentralized system).
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-12-31 1:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-12-21 23:14 what Ruby versions and how many CPU cores/threads are you using? Eric Wong
[not found] ` <CAAtdryMruL6N5nXd0eD_SqFNvTb8=ijs=ti4CTb8SVPfnWj8uw@mail.gmail.com>
2018-12-31 1:01 ` Eric Wong
unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://yhbt.net/unicorn-public
git clone --mirror http://ou63pmih66umazou.onion/unicorn-public
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V1 unicorn-public unicorn-public/ https://yhbt.net/unicorn-public \
unicorn-public@yhbt.net unicorn-public@bogomips.org mongrel-unicorn@rubyforge.org mongrel-unicorn-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
public-inbox-index unicorn-public
Example config snippet for mirrors.
Newsgroups are available over NNTP:
nntp://news.public-inbox.org/inbox.comp.lang.ruby.unicorn
nntp://ou63pmih66umazou.onion/inbox.comp.lang.ruby.unicorn
note: .onion URLs require Tor: https://www.torproject.org/
code repositories for project(s) associated with this inbox:
../../../unicorn.git
AGPL code for this site: git clone http://ou63pmih66umazou.onion/public-inbox.git