Thanks for your reply. I'm on the research side, rather than development. I 
observed 17-22 threads from com.android.browser, suppose only one of those 
thread is doing the real work of rendering the page. 

On 31 Aug 2011, at 22:58, Dianne Hackborn wrote:

> I really don't know what you are trying to get at.  As I said, as far as I 
> know browser CPU use is generally pretty single-threaded -- the DOM rendering 
> and JavaScript interpreter all need to run in the same thread.  Just creating 
> more threads doesn't magically allow this work to be spread across them.
> 
> And again, Gingerbread was not written for multi-core CPUs.  In fact if you 
> try to run stock GB on a multi-core CPU you will be extremely unstable 
> because there are many things not working correctly for SMP, especially ARM 
> SMP.  So it doesn't make sense to ask questions about how stock GB runs on 
> multi-core, because it just doesn't.
> 
> If you are wondering about a particular phone someone has released with GB, 
> you will need to talk with that manufacturer, because they will have needed 
> to do some work to have GB run on a multi-core CPU.
> 
> On Wed, Aug 31, 2011 at 2:09 PM, Jack Harvard <jack.harv...@gmail.com> wrote:
> Thanks for your reply, Dianne. If I run the Android browser as my only 
> application in Gingerbread on a quad-core smartphone, and the page to be 
> loaded is stored locally in memory (no network delay etc, in this case, the 
> browser is single-threaded only as no network connection?), I wouldn't see 
> any performance scaling (or worse, as the OS may move the threads to another 
> core less busy in a circle) from a single-core smartphone, everything else 
> being the same?
> 
> On 31 Aug 2011, at 21:00, Dianne Hackborn wrote:
> 
> > 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 <jack.harv...@gmail.com> 
> > 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 <hack...@android.com> 
> > > wrote:
> > > A few.  Why? :)
> > >
> > >
> > > On Wed, Aug 31, 2011 at 10:40 AM, Jack Harvard <jack.harv...@gmail.com> 
> > > 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 android-developers@googlegroups.com
> > > To unsubscribe from this group, send email to
> > > android-developers+unsubscr...@googlegroups.com
> > > For more options, visit this group at
> > > http://groups.google.com/group/android-developers?hl=en
> > >
> > >
> > >
> > > --
> > > Dianne Hackborn
> > > Android framework engineer
> > > hack...@android.com
> > >
> > > 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
> > > hack...@android.com
> > >
> > > 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 android-developers@googlegroups.com
> > > To unsubscribe from this group, send email to
> > > android-developers+unsubscr...@googlegroups.com
> > > 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 android-developers@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-developers+unsubscr...@googlegroups.com
> > For more options, visit this group at
> > http://groups.google.com/group/android-developers?hl=en
> >
> >
> >
> > --
> > Dianne Hackborn
> > Android framework engineer
> > hack...@android.com
> >
> > 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 android-developers@googlegroups.com
> > To unsubscribe from this group, send email to
> > android-developers+unsubscr...@googlegroups.com
> > 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 android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
> 
> 
> 
> -- 
> Dianne Hackborn
> Android framework engineer
> hack...@android.com
> 
> 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 android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscr...@googlegroups.com
> 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 android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to