Re: [jruby-user] Which Rack web server?
Theo Hultberg <[email protected]> Thu, 30 Apr 2015 09:21:43 +0200
| Newsgroups | gmane.comp.lang.jruby.user |
|---|---|
| Message-ID | <CAMR1f-ca8AxjEd8Ni=0Tp-5Kfc+KjwRis+jnyVM1Sd8JiaiAuw@mail.gmail.com> |
--047d7bdcaa0ec7d2a80514ebf355 Content-Type: text/plain; charset=UTF-8 Christian, my bad, last I checked it was dead, but looking at the repo now it has had some activity. That said, the diff between now and two years ago is just updates between maintenance releases of Jetty and a setting for the min number of threads, so I'll revise my statement to "it basically hasn't been updated in years". That doesn't mean that it's bad or unstable, just that it might be hard to get bugs fixed. T# On Thu, Apr 30, 2015 at 8:10 AM, Christian MICHON < [email protected]> wrote: > @Theo: > > A small correction is needed on this specific sentence: "Mizuno is the > precursor to Fishwife, and it hasn't been updated in years" > > Mizuno had a new release 1 week ago and the last one before was less than > 9 months ago... > > > On Thu, Apr 30, 2015 at 8:00 AM, Theo Hultberg <[email protected]> wrote: > >> Our experience is that there doesn't exist a good, correct, performant >> rack server for JRuby. We've used most of them, for two use cases: embedded >> status APIs in long running applications and as the primary interface for >> applications with a HTTP API. >> >> We package our applications as standalone JAR files with JRuby and all >> gems, and run them with `java -jar ...`, and this rules our some of the >> options. Either because some servers just don't work when run that way >> because they assume they will be able to muck about with the file system >> any way they like, or because they need to be in control, they need to be >> the container of the application. >> >> These are the servers we've tried, and our experience. If your use case >> is different, for example serving Rails apps, this may not be your >> experience: >> >> * Fishwife is the only one we've found that doesn't have significant bugs >> and can be embedded. It's not perfect, but it works well for us. >> >> * Mizuno is the precursor to Fishwife, and it hasn't been updated in >> years. >> >> * Puma is nice and I'd really like to use it, but the error handling is >> buggy. It has often filled up disks with error messages. I think the worst >> of this has been fixed, but in our experience it doesn't handle connection >> errors very well. We stay well away from Puma. >> >> * Jubilee showed some great promise but then development stopped. We >> haven't tried the last released version, but the last version we tried had >> significant bugs around request body handling. >> >> * rack-jetty was abandoned several years ago and doesn't handle request >> bodies over 4 KiB. >> >> * I'm not aware of any major bugs in Trinidad, but it doesn't work when >> embedded. >> >> * Torquebox is also not embeddable, and version 4 is starting to feel >> like vaporware. >> >> * WEBrick works surprisingly well for status APIs that don't get called >> very often. >> >> As I said, our use case is very different from serving a Rails >> application, so your experience will probably be different. >> >> T# >> >> On Wed, Apr 29, 2015 at 12:04 AM, Benjamin Ortega <[email protected]> >> wrote: >> >>> We use Trinidad (multithreaded) and are satisfied with it. It's fast >>> enough and it scales and can be monitored nicely. We use Passenger for MRI >>> apps and have considered standardizing on Passenger or puma for everything, >>> but don't have any specific plans to do so. >>> >>> FWIW I think you have to buy Passenger Enterprise to run your app >>> multithreaded on Passenger. >>> >>> On Tue, Apr 28, 2015 at 4:34 PM, Christian MICHON < >>> [email protected]> wrote: >>> >>>> Mizuno (jetty). >>>> - fastest from what I measured with apache-bench on my machines >>>> - simplest configuration (almost none) >>>> >>>> Only drawback: CTRL-C does not work well on Windows (the java process >>>> will be detached and will keep running), you might need to implement a >>>> shutdown hook in your app. >>>> >>>> On Mon, Apr 27, 2015 at 9:29 PM, Doug Hathaway <[email protected]> >>>> wrote: >>>> >>>>> Tomcat deployed via Warbler. >>>>> >>>>> On Mon, Apr 27, 2015 at 12:55 PM, John Joseph Bachir < >>>>> [email protected]> wrote: >>>>> >>>>>> Which Rack web server are folks using with JRuby? Any particularly >>>>>> bad or good experiences? >>>>>> >>>>>> I suppose the only ones that support threading are Puma and Passenger? >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Doug Hathaway* >>>>> http://www.dadesystems.com/ >>>>> [email protected] >>>>> (407) 680-3631 >>>>> >>>> >>>> >>>> >>>> -- >>>> Christian >>>> >>> >>> >> > > > -- > Christian > --047d7bdcaa0ec7d2a80514ebf355 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Christian, my bad, last I checked it was dead, but looking= at the repo now it has had some activity. That said, the diff between now = and two years ago is just updates between maintenance releases of Jetty and= a setting for the min number of threads, so I'll revise my statement t= o "it=C2=A0basically hasn't been updated in years". That does= n't mean that it's bad or unstable, just that it might be hard to g= et bugs fixed.<div><br></div><div>T#</div></div><div class=3D"gmail_extra">= <br><div class=3D"gmail_quote">On Thu, Apr 30, 2015 at 8:10 AM, Christian M= ICHON <span dir=3D"ltr"><<a href=3D"mailto:[email protected]" t= arget=3D"_blank">[email protected]</a>></span> wrote:<br><block= quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc= solid;padding-left:1ex"><div dir=3D"ltr">@Theo:<div><br></div><div>A small= correction is needed on this specific sentence: "<span style=3D"font-= size:12.8000001907349px">Mizuno is the precursor to Fishwife, and it hasn&#= 39;t been updated in years"</span><div><span style=3D"font-size:12.800= 0001907349px"><br></span></div><div><span style=3D"font-size:12.80000019073= 49px">Mizuno had a new release 1 week ago and the last one before was less = than 9 months ago...<br></span><div><br></div></div></div></div><div class= =3D"gmail_extra"><div><div class=3D"h5"><br><div class=3D"gmail_quote">On T= hu, Apr 30, 2015 at 8:00 AM, Theo Hultberg <span dir=3D"ltr"><<a href=3D= "mailto:[email protected]" target=3D"_blank">[email protected]</a>></span>= wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor= der-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>Our experie= nce is that there doesn't exist a good, correct, performant rack server= for JRuby. We've used most of them, for two use cases: embedded status= APIs in long running applications and as the primary interface for applica= tions with a HTTP API.</div><div><br></div><div>We package our applications= as standalone JAR files with JRuby and all gems, and run them with `java -= jar ...`, and this rules our some of the options. Either because some serve= rs just don't work when run that way because they assume they will be a= ble to muck about with the file system any way they like, or because they n= eed to be in control, they need to be the container of the application.</di= v><div><br></div><div>These are the servers we've tried, and our experi= ence. If your use case is different, for example serving Rails apps, this m= ay not be your experience:</div><div><br></div>* Fishwife is the only one w= e've found that doesn't have significant bugs and can be embedded. = It's not perfect, but it works well for us.<div><br></div><div>* Mizuno= is the precursor to Fishwife, and it hasn't been updated in years.<br>= <div><br></div><div>* Puma is nice and I'd really like to use it, but t= he error handling is buggy. It has often filled up disks with error message= s. I think the worst of this has been fixed, but in our experience it doesn= 't handle connection errors very well. We stay well away from Puma.</di= v><div><br></div><div>* Jubilee showed some great promise but then developm= ent stopped. We haven't tried the last released version, but the last v= ersion we tried had significant bugs around request body handling.</div><di= v><br></div><div>* rack-jetty was abandoned several years ago and doesn'= ;t handle request bodies over 4 KiB.</div><div><br></div><div>* I'm not= aware of any major bugs in Trinidad, but it doesn't work when embedded= .</div><div><br></div><div>* Torquebox is also not embeddable, and version = 4 is starting to feel like vaporware.</div><div><br></div><div>* WEBrick wo= rks surprisingly well for status APIs that don't get called very often.= </div><div><br></div><div>As I said, our use case is very different from se= rving a Rails application, so your experience will probably be different.</= div><span><font color=3D"#888888"><div><br></div><div>T#</div></font></span= ></div></div><div><div><div class=3D"gmail_extra"><br><div class=3D"gmail_q= uote">On Wed, Apr 29, 2015 at 12:04 AM, Benjamin Ortega <span dir=3D"ltr">&= lt;<a href=3D"mailto:[email protected]" target=3D"_blank">ben.ortega@gma= il.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"= margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"= ltr">We use Trinidad (multithreaded) and are satisfied with it. It's fa= st enough and it scales and can be monitored nicely. We use Passenger for M= RI apps and have considered standardizing on Passenger or puma for everythi= ng, but don't have any specific plans to do so.<div><br><div><div><div>= FWIW I think you have to buy Passenger Enterprise to run your app multithre= aded on Passenger.</div></div></div></div></div><div><div><div class=3D"gma= il_extra"><br><div class=3D"gmail_quote">On Tue, Apr 28, 2015 at 4:34 PM, C= hristian MICHON <span dir=3D"ltr"><<a href=3D"mailto:christian.michon@gm= ail.com" target=3D"_blank">[email protected]</a>></span> wrote:= <br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef= t:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Mizuno (jetty).<div>- f= astest from what I measured with apache-bench on my machines</div><div>- si= mplest configuration (almost none)</div><div><br></div><div>Only drawback: = CTRL-C does not work well on Windows (the java process will be detached and= will keep running), you might need to implement a shutdown hook in your ap= p.</div></div><div class=3D"gmail_extra"><div><div><br><div class=3D"gmail_= quote">On Mon, Apr 27, 2015 at 9:29 PM, Doug Hathaway <span dir=3D"ltr"><= ;<a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]= </a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin= :0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">T= omcat deployed via Warbler.</div><div class=3D"gmail_extra"><span><br><div = class=3D"gmail_quote">On Mon, Apr 27, 2015 at 12:55 PM, John Joseph Bachir = <span dir=3D"ltr"><<a href=3D"mailto:[email protected]" target= =3D"_blank">[email protected]</a>></span> wrote:<br><blockquote= class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli= d;padding-left:1ex"><div dir=3D"ltr">Which Rack web server are folks using = with JRuby? Any particularly bad or good experiences?<div><br></div><div>I = suppose the only ones that support threading are Puma and Passenger?</div><= /div> </blockquote></div><br><br clear=3D"all"><div><br></div></span><span><font = color=3D"#888888">-- <br><div><div dir=3D"ltr"><b>Doug Hathaway</b><div><a = href=3D"http://www.dadesystems.com/" target=3D"_blank">http://www.dadesyste= ms.com/</a></div><div><a href=3D"mailto:[email protected]" target=3D"_bl= ank">[email protected]</a><br><a href=3D"tel:%28407%29%20680-3631" value= =3D"+14076803631" target=3D"_blank">(407) 680-3631</a><br></div></div></div= > </font></span></div> </blockquote></div><br><br clear=3D"all"><div><br></div></div></div><span><= font color=3D"#888888">-- <br><div>Christian<br></div> </font></span></div> </blockquote></div><br></div> </div></div></blockquote></div><br></div> </div></div></blockquote></div><br><br clear=3D"all"><div><br></div></div><= /div><span class=3D"HOEnZb"><font color=3D"#888888">-- <br><div>Christian<b= r></div> </font></span></div> </blockquote></div><br></div> --047d7bdcaa0ec7d2a80514ebf355--