Initialize TaskScheduler in remoting processes.

Initialize TaskScheduler in remoting processes.

Added TaskScheduler initialization in the following processes:
 1. It2Me host.
 2. Me2Me host.
 3. Me2Me native messaging host.
 4. Android client.
 5. iOS client.

BUG=687692
Review-Url: https://codereview.chromium.org/2669893002
Cr-Commit-Position: refs/heads/master@{#447676}
Committed: https://chromium.googlesource.com/chromium/src/+/7df3c119b83d5b30eb201c7310141e4f87a326d1

[Sergey Ulanov, 2017-02-01 23:12:44]

sergeyu@chromium.org changed reviewers:
+ joedow@chromium.org, nicholss@chromium.org

[Sergey Ulanov, 2017-02-01 23:13:28]

sergeyu@chromium.org changed reviewers:
+ fdoray@chromium.org

[Sergey Ulanov, 2017-02-01 23:13:28]

+fdoray

[nicholss, 2017-02-01 23:14:47]

LGTM

[joedow, 2017-02-01 23:20:43]

lgtm

https://codereview.chromium.org/2669893002/diff/1/remoting/client/jni/chromot...
File remoting/client/jni/chromoting_jni_runtime.cc (right):

https://codereview.chromium.org/2669893002/diff/1/remoting/client/jni/chromot...
remoting/client/jni/chromoting_jni_runtime.cc:46: const int
kMaxBackgroundThreads = 5;
I see that 5 is used consistently in this CL, is there anything special about
this value?  If so, then a comment would be good.

[Sergey Ulanov, 2017-02-02 00:14:19]

https://codereview.chromium.org/2669893002/diff/1/remoting/client/jni/chromot...
File remoting/client/jni/chromoting_jni_runtime.cc (right):

https://codereview.chromium.org/2669893002/diff/1/remoting/client/jni/chromot...
remoting/client/jni/chromoting_jni_runtime.cc:46: const int
kMaxBackgroundThreads = 5;
On 2017/02/01 23:20:42, joedow wrote:
> I see that 5 is used consistently in this CL, is there anything special about
> this value?  If so, then a comment would be good.

No, there is nothing scientific about this value. It could be 2 or 20, and that
would make no difference in practice. 
FWIW chrome scales number of background threads proportional to number of CPUs.
I don't think it's necessary for chromoting right now, as number of places where
TaskScheduler is used is very limited. Note that chrome also separate different
classes of threads in different pools.
I've added a TODO in each of these 5 places to reconsider the policies,
particularly when TaskScheduler becomes more widely used.

Potentially we could redo threading logic for the host, e.g. it could use
TaskScheduler for the encoder. That would require configuring TaskScheduler to
use separate pool for these tasks.

[Sergey Ulanov, 2017-02-02 00:15:07]

The CQ bit was checked by sergeyu@chromium.org

[Sergey Ulanov, 2017-02-02 00:15:07]

The patchset sent to the CQ was uploaded after l-g-t-m from
nicholss@chromium.org, joedow@chromium.org
Link to the patchset: https://codereview.chromium.org/2669893002/#ps20001
(title: "TODOs")

[commit-bot: I haz the power, 2017-02-02 00:15:57]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-02-02 00:29:04]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-02-02 00:29:05]

Try jobs failed on following builders:
  win_clang on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_clang/builds/...)

[Sergey Ulanov, 2017-02-02 01:28:57]

comp

[Sergey Ulanov, 2017-02-02 01:29:07]

The CQ bit was checked by sergeyu@chromium.org

[Sergey Ulanov, 2017-02-02 01:29:08]

The patchset sent to the CQ was uploaded after l-g-t-m from
nicholss@chromium.org, joedow@chromium.org
Link to the patchset: https://codereview.chromium.org/2669893002/#ps40001
(title: ".")

[commit-bot: I haz the power, 2017-02-02 01:29:27]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-02-02 01:40:20]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1485998947726760,
"parent_rev": "3a4d2a76410d5606a26578e0ae0be4bec5f32d04", "commit_rev":
"7df3c119b83d5b30eb201c7310141e4f87a326d1"}

[commit-bot: I haz the power, 2017-02-02 01:41:30]

Description was changed from

==========
Initialize TaskScheduler in remoting processes.

Added TaskScheduler initialization in the following processes:
 1. It2Me host.
 2. Me2Me host.
 3. Me2Me native messaging host.
 4. Android client.
 5. iOS client.

BUG=687692
==========

to

==========
Initialize TaskScheduler in remoting processes.

Added TaskScheduler initialization in the following processes:
 1. It2Me host.
 2. Me2Me host.
 3. Me2Me native messaging host.
 4. Android client.
 5. iOS client.

BUG=687692

Review-Url: https://codereview.chromium.org/2669893002
Cr-Commit-Position: refs/heads/master@{#447676}
Committed:
https://chromium.googlesource.com/chromium/src/+/7df3c119b83d5b30eb201c731014...
==========

[commit-bot: I haz the power, 2017-02-02 01:41:31]

Committed patchset #3 (id:40001) as
https://chromium.googlesource.com/chromium/src/+/7df3c119b83d5b30eb201c731014...