Status

()

defect
P4
normal
6 years ago
a year ago

People

(Reporter: mak, Unassigned)

Tracking

(Depends on 1 bug, Blocks 2 bugs, {main-thread-io, meta, perf})

unspecified
Points:
---
Dependency tree / graph
Bug Flags:
qe-verify -

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [fxperf][qf:meta])

Reporter

Description

6 years ago
if possible we should move form history to the async only connection, this bug is to track the needed work
Reporter

Updated

6 years ago
Depends on: 888784
Reporter

Updated

5 years ago
Blocks: 987745
Reporter

Comment 1

4 years ago
or use Sqlite.jsm
Whiteboard: [qf]
Flags: qe-verify-
Priority: -- → P2
Whiteboard: [qf] → [photon-performance] [qf]

Updated

2 years ago
Whiteboard: [photon-performance] [qf] → [photon-performance] [qf:p1]
Reporter

Updated

2 years ago
Summary: Use mozIStorageAsyncConnection in Form History → Use Sqlite.jsm in Form History
Priority: P2 → P3
Whiteboard: [photon-performance] [qf:p1] → [reserve-photon-performance] [qf:p1]
Whiteboard: [reserve-photon-performance] [qf:p1] → [reserve-photon-performance] [qf:p2]
Priority: P3 → P4
Keywords: perf
Whiteboard: [reserve-photon-performance] [qf:p2] → [reserve-photon-performance] [perf:p2]

Updated

2 years ago
Whiteboard: [reserve-photon-performance] [perf:p2] → [reserve-photon-performance] [qf:p2]

Updated

2 years ago
Whiteboard: [reserve-photon-performance] [qf:p2] → [reserve-photon-performance] [qf:p1]
Whiteboard: [reserve-photon-performance] [qf:p1] → [reserve-photon-performance] [qf:meta]
Reporter

Comment 2

a year ago
For the most part this has been fixed by bug 888784.
There are still a few callpoints in tests that could be converted, but it's not critical: https://searchfox.org/mozilla-central/search?q=open.*database&case=false&regexp=true&path=satchel
Reporter

Updated

a year ago
No longer blocks: 987745
Reporter

Updated

a year ago
Keywords: main-thread-io
Whiteboard: [reserve-photon-performance] [qf:meta] → [fxperf][qf:meta]
Keywords: meta
(In reply to Marco Bonardo [::mak] from comment #2)

I've opened a new bug for that.
You need to log in before you can comment on or make changes to this bug.