Open Bug 1962423 Opened 27 days ago Updated 6 days ago

Optimize DB writes for Bounce Tracking Protection

Categories

(Core :: Privacy: Anti-Tracking, task, P2)

task

Tracking

()

ASSIGNED

People

(Reporter: emz, Assigned: emz)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

In Bug 1961765 we've seen a performance regression, increased file IO, from widening our classification heuristic. That means we write more tracker candidates to the DB. When a lot of navigation happens, we write a lot to disk. We do one write per classified tracker. This could be made more efficient by batching writes. We can create an in-memory buffer gets written to DB when its full. It should also be written to disk on shutdown. We can restrict this buffer mechanism for bounce tracking candidates, and exclude user activation, if that means more implementation complexity.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: