Closed Bug 1572043 Opened 7 months ago Closed 7 months ago

Versioning in decoder benchmark entries

Categories

(Core :: Audio/Video: Playback, enhancement, P2)

enhancement

Tracking

()

RESOLVED FIXED
mozilla70
Tracking Status
firefox70 --- fixed

People

(Reporter: achronop, Assigned: achronop)

References

Details

Attachments

(3 files)

We want to create a kind of versioning for the benchmark entries that are stored in the database. The versioning will be used to verify that a decoder produces entries for the right version. A version will be a number that follows the benchmark entries in the database.
The way that it works is, for example after a decoder update, we may want to mark the new benchmark entries with a new version. Then all the entries corresponding to the previous version will be erased, from the database, and a new version will be assigned to the new entries.

Add a new method in the key-value wrapper (KeyValueStorage) to clear all the entries of a database.

The new protocol method trasfers the database name and the version number from the content to the parent process. Then the parent process retrieves the stored version number from the database and compares it to the provided version number. If they are the same it stops there, otherwise it erases all the entries from the database and stores the new version number.

Introduce a static method to call the CheckVersion method of the IPDL protocol from the content process. Every time a video decoder is initialized, the method is called to verify the version of the stored benchmark entries.

Blocks: 1573184
Pushed by achronopoulos@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/7d2c4b21d1bf
Introduce a method to clear all the entries of a database.r=jya
https://hg.mozilla.org/integration/autoland/rev/1c3d1685235f
Introduce a check version method in the benchmark storage IPDL protocol.r=jya
https://hg.mozilla.org/integration/autoland/rev/fab2d14c089f
Check the version of the stored benchmarks when a video decoder is initialized.r=jya
You need to log in before you can comment on or make changes to this bug.