Delete the ClientSocketPoolHistograms class.

Delete the ClientSocketPoolHistograms class.

This class write the
Net.SocketIdleTimeBeforeNextUse_ReusedSocket
Net.SocketIdleTimeBeforeNextUse_UnusedSocket
Net.SocketInitErrorCodes
Net.SocketRequestTime
Net.SocketType
histograms.

This histograms are all unowned, and have a large cumulative load on user bandwidth and internal google servers.
Are these histograms used at all? It appears they have not been used for some time (based on lack of ownership)

BUG=469288
Committed: https://crrev.com/d90695c943f92eac547ee04ad0913f6e316258de
Cr-Commit-Position: refs/heads/master@{#322244}

[rkaplow, 2015-03-20 19:51:26]

rkaplow@chromium.org changed reviewers:
+ cbentzel@chromium.org, isherman@chromium.org

[rkaplow, 2015-03-20 19:51:27]

isherman@chromium.org: Please review changes in 
histograms

cbentzel@chromium.org: Please review changes in 

All

[Ilya Sherman, 2015-03-20 19:57:09]

histograms.xml lgtm

[rkaplow, 2015-03-23 15:52:29]

rkaplow@chromium.org changed reviewers:
+ mmenke@chromium.org

[rkaplow, 2015-03-24 14:49:53]

On 2015/03/23 15:52:30, rkaplow wrote:

Is there a better person to review this CL?

[mmenke, 2015-03-25 15:41:13]

LGTM.

I think we can safely get rid of all of these.  We may want to bring something
back in the future, but if so, I think we can manage much cleaner plumbing than
this, and we don't need to split everything up by type, like we did before.

[mmenke, 2015-03-25 15:42:00]

On 2015/03/25 15:41:13, mmenke wrote:
> LGTM.
> 
> I think we can safely get rid of all of these.  We may want to bring something
> back in the future, but if so, I think we can manage much cleaner plumbing
than
> this, and we don't need to split everything up by type, like we did before.

And if we bring something back, it would presumably be for a specific
experiment, and not necessarily something we'd want to keep, long term.

[rkaplow, 2015-03-25 20:51:00]

On 2015/03/25 15:42:00, mmenke wrote:
> On 2015/03/25 15:41:13, mmenke wrote:
> > LGTM.
> > 
> > I think we can safely get rid of all of these.  We may want to bring
something
> > back in the future, but if so, I think we can manage much cleaner plumbing
> than
> > this, and we don't need to split everything up by type, like we did before.
> 
> And if we bring something back, it would presumably be for a specific
> experiment, and not necessarily something we'd want to keep, long term.


Sounds good. THanks, submitting now

[rkaplow, 2015-03-25 20:51:10]

The CQ bit was checked by rkaplow@chromium.org

[commit-bot: I haz the power, 2015-03-25 20:51:25]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1027693004/20001

[commit-bot: I haz the power, 2015-03-25 22:13:13]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-03-25 22:13:53]

Patchset 2 (id:??) landed as
https://crrev.com/d90695c943f92eac547ee04ad0913f6e316258de
Cr-Commit-Position: refs/heads/master@{#322244}