Right. You need to use a nonblocking database driver to do concurrent requests.

You can do this with neverblock's database drivers and Active Record
adapter (http://www.espace.com.eg/neverblock/benchmarks) or with
jruby.

Best,
jeremy

On Sun, Nov 16, 2008 at 5:25 AM, kang peng <[EMAIL PROTECTED]> wrote:
> ok, so i think ActiveRecord is thread safe, right? if so, each request which
> call to database will be processed one by one, not concurrent, this seems
> RoR's will be not good when faces big amont of requests in a short time. is
> it ture?
>
> On Sun, Nov 16, 2008 at 7:24 PM, Jeremy Kemper <[EMAIL PROTECTED]> wrote:
>>
>> No, just one connection.
>>
>> On Sat, Nov 15, 2008 at 10:18 PM, kang peng <[EMAIL PROTECTED]> wrote:
>> > thanks. so before Rails2.2, each request will open new connection to
>> > database according to 'Active Record uses a single persistent
>> > connection per thread'? because as i know, each request will start a new
>> > thread, is it correct?
>> >
>> > On Sun, Nov 16, 2008 at 12:29 PM, Jeremy Kemper <[EMAIL PROTECTED]>
>> > wrote:
>> >>
>> >> On Sat, Nov 15, 2008 at 8:11 PM, Kang Peng <[EMAIL PROTECTED]> wrote:
>> >> > does anyone know whether ActiveRecord has supported connection pool?
>> >> > i
>> >> > can't find articles talking about this, if so how to control it in
>> >> > Rails apps.
>> >>
>> >> In Rails 2.1 and earlier, Active Record uses a single persistent
>> >> connection per thread.
>> >>
>> >> Beginning in Rails 2.2, Active Record uses a connection pool. Install
>> >> the 2.2rc2 release and give it a spin.
>> >>
>> >> Best,
>> >> jeremy
>> >>
>> >>
>> >
>> >
>> > >
>> >
>>
>>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to