Track size of VideoDecodeStatsDB via UMA |
||
Issue descriptionIts a good idea to set up a UMA to see size in the wild and add some chirp alerts if things change drastically. We anticipate the size on disk to be a few dozen KB. Absolute max size could be 22MB (if you played every type of media in every possible framerate and resolution... no one does this). This is also gives insight into how much of the shared DB cache we could theoretically use.
,
Sep 24
+thildebr and +ssid while I'm out.
,
Sep 25
If the DB folder only contains the DB then I don't see any problem with measuring its size using something like base::ComputeDirectorySize. When you say how much of the shared DB cache you could theoretically use, you're referring to the shared 8MB block cache? Are you trying to ensure that you're keeping this number low? Most users of ProtoDatabase end up loading entries from the database once and cache them locally in their de-serialized proto form which means that there's really no use to the read cache at all. If this is the case, it might be worth me adding Get/GetEntry functions that allow custom ReadOptions to avoid filling the read cache at all. |
||
►
Sign in to add a comment |
||
Comment 1 by chcunningham@chromium.org
, Sep 20