New issue
Advanced search Search tips

Issue 852654 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Aug 31
Cc:
falken@chromium.org
wanderview@chromium.org
kinuko@chromium.org
shimazu@chromium.org
pwnall@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Task



Sign in to add a comment

Having performance related UMAs for CacheStorage API (esp. cache.match())

Project Member Reported by shimazu@chromium.org, Jun 14 2018 
cache.match() is one of the core functionality for service worker usage. We already have UMAs for health checking, but we currently can't see the performance related numbers (is my understanding correct?).
Let's add those to get performance insights.

Comment 1 by wanderview@chromium.org, Aug 31

Status: WontFix (was: Available)
We have a set of histograms here:

  go/cache-storage-uma (internal only)

This includes round-trip timing of operations like cache.match() as ServiceWorkerCache.Cache.Match2.

I'm going to close this as wontfix for now since I think we already have the basics.  If there are other specific things you'd like to see measured, please re-open or file a new issue.  Thanks!

Comment 2 by pwnall@chromium.org, Aug 31

Cc: wanderview@chromium.org
+cc wanderview@ so comments show up on your radar
►

Sign in to add a comment