Count exact cache size for time ranges

Currently cache size in "Clear browsing data" dialog is shown as "Less than X" when selecting a time range (Where X is the total size of the cache).
To fix this, I count the cache size depending on a chosen time range.
The cache can be very big and we want a responsive ui, so if counting the cache takes too long I show the upper estimate instead.

As a future improvement I would like to propose a specialized version for SimpleBackendImpl. It could determine the size of a subset of the cache from the EntryMetadata stored in memory. This should be fast enough for any cache size.

BUG=671196
CQ-DEPEND=CL:2591743002

[dullweber, 2017-01-04 15:06:06]

Description was changed from

==========
Currently cache size in "Clear browsing data" dialog is shown as "Less than X"
when selecting a time range (Where X is the total size of the cache).
To fix this, I count the cache size depending on a chosen time range.
The cache can be very big and we want a responsive ui, so if counting the cache
takes too long I show the upper estimate instead.

As a future improvement I would like to propose a specialized version for
SimpleBackendImpl. It could determine the size of a subset of the cache from the
EntryMetadata stored in memory. This should be fast enough for any cache size.

BUG=671196
CQ-DEPEND=CL:2591743002
==========

to

==========
Currently cache size in "Clear browsing data" dialog is shown as "Less than X"
when selecting a time range (Where X is the total size of the cache).
To fix this, I count the cache size depending on a chosen time range.
The cache can be very big and we want a responsive ui, so if counting the cache
takes too long I show the upper estimate instead.

As a future improvement I would like to propose a specialized version for
SimpleBackendImpl. It could determine the size of a subset of the cache from the
EntryMetadata stored in memory. This should be fast enough for any cache size.

BUG=671196
CQ-DEPEND=CL:2591743002
==========

[dullweber, 2017-01-04 15:07:02]

The CQ bit was checked by dullweber@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-01-04 15:07:12]

Dry run: 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-01-04 15:21:47]

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

[commit-bot: I haz the power, 2017-01-04 15:21:48]

Dry run: Try jobs failed on following builders:
  android_compile_dbg on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_comp...)

[dullweber, 2017-01-05 09:21:16]

The CQ bit was checked by dullweber@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-01-05 09:21:39]

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

[dullweber, 2017-01-05 09:23:50]

dullweber@chromium.org changed reviewers:
+ msramek@chromium.org

[dullweber, 2017-01-05 09:23:50]

The cl with the code removed from http://crrev.com/2556363003

[msramek, 2017-01-05 09:34:30]

LGTM

[commit-bot: I haz the power, 2017-01-05 10:17:13]

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

[commit-bot: I haz the power, 2017-01-05 10:17:13]

Dry run: This issue passed the CQ dry run.