From olio-user-return-440-apmail-incubator-olio-user-archive=incubator.apache.org@incubator.apache.org Fri Jun 11 06:57:07 2010 Return-Path: Delivered-To: apmail-incubator-olio-user-archive@minotaur.apache.org Received: (qmail 23216 invoked from network); 11 Jun 2010 04:08:40 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 11 Jun 2010 04:08:40 -0000 Received: (qmail 18073 invoked by uid 500); 11 Jun 2010 04:08:40 -0000 Delivered-To: apmail-incubator-olio-user-archive@incubator.apache.org Received: (qmail 18024 invoked by uid 500); 11 Jun 2010 04:08:39 -0000 Mailing-List: contact olio-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: olio-user@incubator.apache.org Delivered-To: mailing list olio-user@incubator.apache.org Received: (qmail 18016 invoked by uid 99); 11 Jun 2010 04:08:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jun 2010 04:08:38 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of brgsousa@gmail.com designates 209.85.211.197 as permitted sender) Received: from [209.85.211.197] (HELO mail-yw0-f197.google.com) (209.85.211.197) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Jun 2010 04:08:32 +0000 Received: by ywh35 with SMTP id 35so578053ywh.29 for ; Thu, 10 Jun 2010 21:08:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=0ybUosxEzqOLMCb23GW9Erjrqjk8fuyH5YHrB8hshf8=; b=Mkv429lcxrZ5VceqhAWNE9CLwqCIXC3OKqCj3ROQTvpFQKPJbnHu+AjHI5aWIQLeRh dtoB0z6RtRA1aD5gRPwc4+B0YPvWKH0xG/f30/K6cxBU3xplekyYf2CpT8ILxQMpBnq3 zserCAFG+OcJ8OCnU/Ky/g27yie1+ZLt9abcM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=L44mNOTpWwDKfQ8QIt6rdjIy5JelfIB+DKWxPaXyRERlkUXoeD+QOc5Pj1quwUzeUD 2TbkbEY9kC9Woi9jqg4b03ymPo7mDFsFGXlPGFNOXvK9eD+V7yhFAdaIZTk2P8TRTMdm FR9BRPJLNdXuqAc40+1+ziknMogDYKzIHAAj0= Received: by 10.91.156.8 with SMTP id i8mr2002069ago.187.1276229291154; Thu, 10 Jun 2010 21:08:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.90.101.8 with HTTP; Thu, 10 Jun 2010 21:07:51 -0700 (PDT) In-Reply-To: References: From: =?ISO-8859-1?Q?Bruno_Guimar=E3es_Sousa?= Date: Fri, 11 Jun 2010 01:07:51 -0300 Message-ID: Subject: Re: Thread safe To: olio-user@incubator.apache.org Content-Type: multipart/alternative; boundary=001485f945dc8d221d0488b9497d X-Virus-Checked: Checked by ClamAV on apache.org --001485f945dc8d221d0488b9497d Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I agree with you. That's what I, in a way or another, tried to mean :) -- Bruno Guimar=E3es Sousa www.ifba.edu.br PONTONET - DGTI - IFBA Ci=EAncia da Computa=E7=E3o UFBA Registered Linux user #465914 On Thu, Jun 10, 2010 at 6:34 PM, Amanda Waite wrote: > > > 2010/6/10 Bruno Guimar=E3es Sousa > > I forgot about rails plugins (for example attachment_fu or >> calendar_helper), but what I really meant was rubygems used by Olio: rco= v, >> will_paginate, image_science and RubyInline. >> >> In short, Olio, maybe, is thread-safe or not, and there's a need for mor= e >> tests in order to prove it right? Maybe plugins/gems developers would be= the >> right folks to answer if each one is thread-safe or not. And then we cou= ld >> conclude how would Olio would work. What do you think? > > > I don't really agree, these are not parts of Olio, they are part of what > Olio is designed to test. Olio Rails does use image_science but you can > easily plugin in rmagick or mini-magick. You can use Thin or Mongrel or > Passenger for the app server component, etc. You seem to be working on th= e > principle that Olio is more than what it is, which is an application and > Faban driver that can be used to test under extreme load, deployment > configurations which include Ruby runtimes and gems as well as operating > systems and hardware. rcov and will_paginate are probably exceptions to > this, although Olio does not force you to use specific versions of these > gems. There are limitations, Rails changes from version to version and so= we > do have to say that we only 'support' specific versions of Rails. Persona= lly > my aim would be for Olio Rails to run on just about anything that you thr= ow > at it and this extends to the plugins that it's bundled with. > > Amanda > > > >> >> regards, >> -- >> Bruno Guimar=E3es Sousa >> www.ifba.edu.br >> PONTONET - DGTI - IFBA >> Ci=EAncia da Computa=E7=E3o UFBA >> Registered Linux user #465914 >> >> >> On Wed, Jun 9, 2010 at 11:59 AM, Amanda Waite < >> amandarwaite@googlemail.com> wrote: >> >>> >>> >>> 2010/6/9 Bruno Guimar=E3es Sousa >>> >>> Hi, >>>> Rails application cores are thread safe since 2.2 version( >>>> http://guides.rubyonrails.org/2_2_release_notes.html#thread-safety). S= o >>>> I suppose Olio's core is thread safe. >>>> >>> >>> That's an interesting question and one that I can only offer empirical >>> evidence on. We've run Olio Rails with most of the available runtime >>> infrastructures from WEBrick to Passenger with both green threaded and >>> native threaded Ruby 1.8 implementations and we've not encountered any >>> issues. On some of our rigs we've run Olio on JRuby on systems with lar= ge >>> numbers of hardware theads. >>> >>> >>> Are Olio's gems able to work with threadsin order to achieve full threa= d >>>> support? >>>> >>> >>> It's impossible to say for sure, they are off the shelf plugins (you do >>> mean the plugins right?) but that doesn't necessarily mean that the >>> versions used in Olio have been tested for thread safety. Again empiric= al >>> evidence is all I can offer. >>> >>> It's something that we can address properly when we add support for Rub= y >>> 1.9. >>> >>> If you meant infrastructure gems such as thin, rack and the MySQL gem >>> then they would be considered parts of the System Under Test and if the= re >>> are any concurrency/thread-safety issues with these then Olio is the ve= ry >>> tool that you need to identify them. >>> >>> Amanda >>> >>> >>> >>>> >>>> regards, >>>> -- >>>> Bruno Guimar=E3es Sousa >>>> www.ifba.edu.br >>>> PONTONET - DGTI - IFBA >>>> Ci=EAncia da Computa=E7=E3o UFBA >>>> Registered Linux user #465914 >>>> >>> >>> >> > --001485f945dc8d221d0488b9497d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I agree with you. That's what I, in a way or another, tried to mean :)<= br>

--
Bruno Guimar=E3es Sousa
www.ifba.edu.br
PONTONET - DGTI - IFBA
Ci=EAnci= a da Computa=E7=E3o UFBA
Registered Linux user #465914


On Thu, Jun 10, 2010 at 6:34 PM, Amanda = Waite <= amandarwaite@googlemail.com> wrote:


2010/6/10 Bruno Guimar=E3es Sousa <brg= sousa@gmail.com>

I forgot about rails plugins (for example attachment_fu or calendar_helper)= , but what I really meant was rubygems used by Olio: rcov, will_paginate, i= mage_science and RubyInline.

In short, Olio, maybe, is thread-safe o= r not, and there's a need for more tests in order to prove it right? Ma= ybe plugins/gems developers would be the right folks to answer if each one = is thread-safe or not. And then we could conclude how would Olio would work= . What do you think?

I don't really agree, these are not parts of Olio, they = are part of what Olio is designed to test. Olio Rails does use image_scienc= e but you can easily plugin in rmagick or mini-magick. You can use Thin or = Mongrel or Passenger for the app server component, etc. You seem to be work= ing on the principle that Olio is more than what it is, which is an applica= tion and Faban driver that can be used to test under extreme load, deployme= nt configurations which include Ruby runtimes and gems as well as operating= systems and hardware. rcov and will_paginate are probably exceptions to th= is, although Olio does not force you to use specific versions of these gems= . There are limitations, Rails changes from version to version and so we do= have to say that we only 'support' specific versions of Rails. Per= sonally my aim would be for Olio Rails to run on just about anything that y= ou throw at it and this extends to the plugins that it's bundled with. =

Amanda




regards,
--
Bruno Guimar=E3es Sousa
www.ifba.edu.br
PONTONET - DGTI - IFBACi=EAncia da Computa=E7=E3o UFBA
Registered Linux user #465914


On Wed, Jun 9= , 2010 at 11:59 AM, Amanda Waite <amandarwaite@googlemail.com> wrote:


2010/6/9 Bruno Guimar=E3es Sousa <brgs= ousa@gmail.com>

Hi,
Rails application cores are thread safe since 2.2 version(http://guides.rubyonrails.org/2_2_release_notes.html#thread-saf= ety). So I suppose Olio's core is thread safe.

That's an interesting question and one that= I can only offer empirical evidence on. We've run Olio Rails with most= of the available runtime infrastructures from WEBrick to Passenger with bo= th green threaded and native threaded Ruby 1.8 implementations and we'v= e not encountered any issues. On some of our rigs we've run Olio on JRu= by on systems with large numbers of hardware theads.



Amanda

=A0

regards,
--
Bruno Guimar=E3es Sousa
www.ifba.edu.brPONTONET - DGTI - IFBA
Ci=EAncia da Computa=E7=E3o UFBA
Registered Linux user #465914




--001485f945dc8d221d0488b9497d--