Unpack extensions.sqlite from omni.jar when profile is created

RESOLVED WONTFIX

Status

()

RESOLVED WONTFIX
7 years ago
5 years ago

People

(Reporter: vladan, Assigned: vladan)

Tracking

({perf})

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

7 years ago
Created attachment 571816 [details] [diff] [review]
Code for unpacking the DB when profile is created

To improve first run performance, we will be unpacking pre-created SQLite databases from omni.jar on profile initialization (see bug 691268).

This change extracts formhistory.sqlite from omni.jar when the database doesn't exist. The extracted DB contains the DB schema but no rows. If extraction fails for whatever reason, an error is logged and the DB is created from scratch as before.
(Assignee)

Updated

7 years ago
Attachment #571816 - Attachment is patch: true
For mobile we don't create extensions.sqlite on startup so this will degrade Ts there
(Assignee)

Updated

7 years ago
Blocks: 691268
Keywords: perf
(Assignee)

Updated

7 years ago
Assignee: nobody → vdjeric
(Assignee)

Updated

7 years ago
Attachment #571816 - Flags: review?(dtownsend)
(Assignee)

Comment 2

7 years ago
(In reply to Dave Townsend (:Mossop) from comment #1)
> For mobile we don't create extensions.sqlite on startup so this will degrade
> Ts there

But then XPIDatabase.openConnection() would never be called on mobile so we would never extract the DB from omni.jar. It's on the same path as DB creation.
Comment on attachment 571816 [details] [diff] [review]
Code for unpacking the DB when profile is created

With all the changes lately we'll need a new patch here. I'd really like to see a conclusion in bug 699615 first though.
Attachment #571816 - Flags: review?(dtownsend)
this db doesn't exist anymore
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.