Gingerbread isn't designed for multi-core CPUs.  The browser doesn't try to
create threads to use multiple CPUs, it creates threads to have multiple
network connections.

Besides networking, browsers are pretty intrinsically single-threaded
anyway.  The complicated stuff all needs to run in one thread: DOM
rendering, JavaScript, etc.

On Wed, Aug 31, 2011 at 12:08 PM, Jack Harvard <[email protected]>wrote:

> I want to understand how many threads Gingerbread generates in order to
> understand how the browser performance scale with multicores? For example,
> if  "a few " means 2, that means 4 cores wouldn't scale the browser
> performance by anywhere close to 4 times. I understand that Gingerbread
> doesn't officially support SMP, sometimes browser does crash on multicore
> platforms, it's not a problem for me though.
>
> On 31 Aug 2011, at 18:57, Dianne Hackborn wrote:
>
> > Oh and Gingerbread wasn't designed to run on anything but single CPU
> systems, so that's irrelevant to the question of the base platform.  Of
> course people shipping Android modify it in various ways, and the browser is
> often one of the things they modify.
> >
> > On Wed, Aug 31, 2011 at 10:57 AM, Dianne Hackborn <[email protected]>
> wrote:
> > A few.  Why? :)
> >
> >
> > On Wed, Aug 31, 2011 at 10:40 AM, Jack Harvard <[email protected]>
> wrote:
> > Wondering how many threads does android browser generate? Suppose it's
> Gingerbread running on a dual-core or quad-core ARM processor.
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Android Developers" 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/android-developers?hl=en
> >
> >
> >
> > --
> > Dianne Hackborn
> > Android framework engineer
> > [email protected]
> >
> > Note: please don't send private questions to me, as I don't have time to
> provide private support, and so won't reply to such e-mails.  All such
> questions should be posted on public forums, where I and others can see and
> answer them.
> >
> >
> >
> >
> > --
> > Dianne Hackborn
> > Android framework engineer
> > [email protected]
> >
> > Note: please don't send private questions to me, as I don't have time to
> provide private support, and so won't reply to such e-mails.  All such
> questions should be posted on public forums, where I and others can see and
> answer them.
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Android Developers" 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/android-developers?hl=en
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" 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/android-developers?hl=en
>



-- 
Dianne Hackborn
Android framework engineer
[email protected]

Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails.  All such
questions should be posted on public forums, where I and others can see and
answer them.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" 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/android-developers?hl=en

Reply via email to