incubator-olio-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Guimarães Sousa <brgso...@gmail.com>
Subject Re: Thread safe
Date Fri, 11 Jun 2010 04:07:51 GMT
I agree with you. That's what I, in a way or another, tried to mean :)


--
Bruno Guimarães Sousa
www.ifba.edu.br
PONTONET - DGTI - IFBA
Ciência da Computação 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ães Sousa <brgsousa@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, image_science and RubyInline.
>>
>> In short, Olio, maybe, is thread-safe or not, and there's a need for more
>> 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 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_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 the
> 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. Personally
> my aim would be for Olio Rails to run on just about anything that you throw
> at it and this extends to the plugins that it's bundled with.
>
> Amanda
>
>
>
>>
>> regards,
>> --
>> Bruno Guimarães Sousa
>> www.ifba.edu.br
>> PONTONET - DGTI - IFBA
>> Ciência da Computação 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ães Sousa <brgsousa@gmail.com>
>>>
>>> Hi,
>>>> Rails application cores are thread safe since 2.2 version(
>>>> http://guides.rubyonrails.org/2_2_release_notes.html#thread-safety). 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 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 large
>>> numbers of hardware theads.
>>>
>>>
>>> Are Olio's gems able to work with threadsin order to achieve full thread
>>>> 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 empirical
>>> evidence is all I can offer.
>>>
>>> It's something that we can address properly when we add support for Ruby
>>> 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 there
>>> are any concurrency/thread-safety issues with these then Olio is the very
>>> tool that you need to identify them.
>>>
>>> Amanda
>>>
>>>
>>>
>>>>
>>>> regards,
>>>> --
>>>> Bruno Guimarães Sousa
>>>> www.ifba.edu.br
>>>> PONTONET - DGTI - IFBA
>>>> Ciência da Computação UFBA
>>>> Registered Linux user #465914
>>>>
>>>
>>>
>>
>

Mime
View raw message