Update ProtocolPerfTest to run host and client on different threads

Update ProtocolPerfTest to run host and client on different threads

Previously the host and client were running on the main thread, so they
both would compete for it and that skews the perf numbers, particularly
with NSS SSL sockets because they use a separate thread.

BUG=394067
R=rmsousa@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=285738

[rmsousa, 2014-07-23 00:49:37]

lgtm

https://codereview.chromium.org/414443009/diff/20001/remoting/signaling/fake_...
File remoting/signaling/fake_signal_strategy.cc (right):

https://codereview.chromium.org/414443009/diff/20001/remoting/signaling/fake_...
remoting/signaling/fake_signal_strategy.cc:124: buzz::XmlElement* stanza_ptr =
stanza.get();
nit: DCHECK current thread?

[Sergey Ulanov, 2014-07-25 18:21:35]

The CQ bit was checked by sergeyu@chromium.org

[Sergey Ulanov, 2014-07-25 18:21:44]

The CQ bit was unchecked by sergeyu@chromium.org

[Sergey Ulanov, 2014-07-25 18:23:16]

https://codereview.chromium.org/414443009/diff/20001/remoting/signaling/fake_...
File remoting/signaling/fake_signal_strategy.cc (right):

https://codereview.chromium.org/414443009/diff/20001/remoting/signaling/fake_...
remoting/signaling/fake_signal_strategy.cc:124: buzz::XmlElement* stanza_ptr =
stanza.get();
On 2014/07/23 00:49:37, rmsousa wrote:
> nit: DCHECK current thread?

Done.

[Sergey Ulanov, 2014-07-25 18:23:18]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2014-07-25 18:24:19]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/sergeyu@chromium.org/414443009/60001

[commit-bot: I haz the power, 2014-07-25 20:26:15]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  win_chromium_x64_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_x64_rel/...)

[Sergey Ulanov, 2014-07-26 00:44:22]

Committed patchset #4 manually as r285738 (presubmit successful).