Judging by extensive list of histograms in the blocking bugs, I suggest you might want to approach this by auditing all Sqlite.* histograms rather than sifting individually through each histogram in the blocking bugs.  I imagine the blocking bugs cover most Sqlite.* histograms.

 Issue 758345  has been merged into this issue.

Issue 694364 has been merged into this issue.
Issue 694366 has been merged into this issue.
Issue 694367 has been merged into this issue.
Issue 708028 has been merged into this issue.
Issue 708040 has been merged into this issue.
Issue 734863 has been merged into this issue.
Issue 734864 has been merged into this issue.
Issue 734866 has been merged into this issue.
Issue 734867 has been merged into this issue.
Issue 736981 has been merged into this issue.
Issue 745190 has been merged into this issue.
Issue 745194 has been merged into this issue.
Issue 755430 has been merged into this issue.
Issue 755433 has been merged into this issue.

Issue 766418 has been merged into this issue.

Issue 766419 has been merged into this issue.

Issue 766421 has been merged into this issue.

Issue 766422 has been merged into this issue.

Issue 768641 has been merged into this issue.

Issue 775340 has been merged into this issue.

Issue 775338 has been merged into this issue.

Issue 777694 has been merged into this issue.

Issue 777697 has been merged into this issue.

Issue 797612 has been merged into this issue.

Issue 802112 has been merged into this issue.

Issue 804642 has been merged into this issue.

Issue 807142 has been merged into this issue.

from pasko@:
Even though Sqlite.SizeKB is not very actionable, I see a lot of value in per-database size histograms. As we develop new features, various databases may bloat and we will need to be able to see the biggest RAM consumers.

Issue 811587 has been merged into this issue.

Issue 811588 has been merged into this issue.

Issue 811592 has been merged into this issue.

Issue 823575 has been merged into this issue.

Issue 823574 has been merged into this issue.

Issue 823572 has been merged into this issue.

Issue 823571 has been merged into this issue.

It looks like these histograms are using upward of one terabyte of storage a day.

That sounds like a lot to me, both in terms of storage and in terms of users' bandwidth.

Can you please look into whether any of these can be retired?

Issue 826119 has been merged into this issue.

Issue 831007 has been merged into this issue.

Issue 795999 has been merged into this issue.

Issue 842965 has been merged into this issue.

Issue 842964 has been merged into this issue.

Issue 842974 has been merged into this issue.

Issue 854021 has been merged into this issue.

Issue 854015 has been merged into this issue.

Issue 854017 has been merged into this issue.

Issue 856432 has been merged into this issue.

Issue 856427 has been merged into this issue.

Issue 862009 has been merged into this issue.

I'm going to put forward a straw-man proposal and suggest that we set all Sql histograms to expire today.

Objections?

CC gayane@ in case such a blanket change is frown upon.  It seems the current inherited sql database owners aren't in a hurry to sort through the histograms to identify the actually useful ones.

Seems reasonable to me - given they're owned by someone who's no longer on Chrome.

We still have the ability to resurrect them from the server-side, if there's a real need.

I'll start an internal thread to better understand the priority of this. Sorry, to me P3 means it's ok to not be in a hurry about a bug. We're generally focusing on P1s.

Issue 864315 has been merged into this issue.

Issue 864316 has been merged into this issue.

Issue 864317 has been merged into this issue.

Issue 864318 has been merged into this issue.

>>>
I'll start an internal thread to better understand the priority of this.
>>>

I don't see the thread.  Can you please add me to it?

Done, and pinged you on IM.

Please reach out to me over e-mail or IM when you have time so we can figure this out.

Issue 878214 has been merged into this issue.

Issue 878217 has been merged into this issue.

Issue 884972 has been merged into this issue.

Issue 884973 has been merged into this issue.

Issue 884974 has been merged into this issue.

setting a NextAction for when pwnall@ returns.

If you can't decide if you want to delete these, maybe you can as a band-aid simply expire them all, and re-enable them when needed?
https://chromium.googlesource.com/chromium/src.git/+/HEAD/tools/metrics/histograms/README.md#histogram-expiry

Issue 891135 has been merged into this issue.

The NextAction date has arrived: 2018-10-04

Issue 893408 has been merged into this issue.

Issue 908716 has been merged into this issue.

Issue 908714 has been merged into this issue.

Issue 915994 has been merged into this issue.

Issue 915989 has been merged into this issue.

Can we do something about these?  I'll not that histogram eraser only files bugs for histograms that are in the top 20 unused histograms for the given time period.

If you can't decide if you want to delete these, maybe you can as a band-aid simply expire them all, and re-enable them when needed?
https://chromium.googlesource.com/chromium/src.git/+/HEAD/tools/metrics/histograms/README.md#histogram-expiry

Issue 919727 has been merged into this issue.