Why Chrome for android has only a single IO thread for Network?

[Coomy Gau]

 I have some problerms about Chromium Network Stack. Hope some one could help me.

 I take charge of the network optimizing in my team ,and our browser[Android Platform] is  switch to [Chromium Network Stack] last year which used to be Java-Net..

I want to know why Chromium Network has only a single thread (which we set 7 in Java-net) to charge the Network task? During the first second I navigate a website, the network thread(IO thread) is so busy that a lot of tasks we post are delayed a lot, because the io-thread is filled up with too many tasks, cpu could only process them in order.

Are there any documents or articles, papers to prove Chrome needs only one thread to charge all network tasks? or prove that  single IO thread is not the bottleneck of Chrome ? Hope someone could help me , and give me some advice. 

[William Chan (陈智昌)]

The Chromium browser IO thread indeed sometimes gets CPU bottlenecked on Chromium/Android. Adding more threads doesn't solve the problem, because at the points where the browser IO thread is CPU bottlenecked, most cores are saturated (by the renderer process), so extra threading doesn't help. I'm talking mostly in general terms, although there are definitely exceptions to this statement. If you've got data that the browser IO thread is getting backed up while other cores are idle, then that would be interesting data to examine. An about:tracing trace would be excellent to see. See http://dev.chromium.org/developers/how-tos/trace-event-profiling-tool for details.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Coomy Gau]

Thanks a lot ! I will think it over earnestly。

在 2014年5月16日星期五UTC+8下午1时16分50秒，William Chan写道：