Oops I see the forum is moderated.. again Sorry for the duplicate... On Thursday, August 20, 2015 at 9:28:28 AM UTC-5, Dale Ackerman wrote: > > ( I am sorry if I duplicated this. I didn't get a confirmation ) > > I am confused by the many posts and other documents and posts regarding > how passenger works with JRuby (fork process or spawn thread) and how that > impacts non rails(ActiveRecord) connection pools. I have inherited a bunch > of ruby (rails/sinatra) application all running on some combination of > Apache2 and passenger both ruby/jruby. I am not convinced that the > configuration are correct. So I need to understand the facts regarding DB > connection pool sharing (if it does) and the differences in methods used > for allocating threads (JRuby JVM) and or forking new OS processes. > > If I have a pool of 10 connection and Passenger spins up 5 instances does > that mean I have 50 connection? Does that mean that only 1 connection is > used process? How is MRI Ruby different from JRuby from a Sequel > perspective? > > stack #1 > ------------------------------------ > Apache2 > Passenger 4/5 > JRuby > Sinatra > Sequel ORM (jdbc drivers) > > stack #2 > ------------------------------------ > Apache2 > Passenger 4/5 > MRI Ruby 1.9 - 2.2.2 > Rails 3.x - 4.x > ActiveRecord ORM (MSSQL freeTDS drivers and some Postgresql) > > I am placing this same question to the Phusion Passenger group as well. I > hope to find the official answer and get that posted in both projects > documentation. > > > Best Regards >
-- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
