Open
Bug 1919688
Opened 10 days ago
Updated 3 days ago
Add PerfStats in more places in a11y code
Categories
(Core :: Disability Access APIs, task)
Core
Disability Access APIs
Tracking
()
NEW
People
(Reporter: Jamie, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [a11yPerf24h2])
After discussion with the performance team, we've determined that PerfStats are likely to be the most helpful measurements in determining performance improvements/regressions in accessibility code. To that end, we want to add PerfStats in a bunch of additional places which are potential hot paths. To make diagnosis easier, all PerfStats should also have corresponding profile markers.
- a11y::PlatformShowHideEvent: Firing show and hide events to the OS.
- DocAccessible::ContentRemoved
- DocAccessible::PruneOrInsertSubtree: Deciding whether to add or remove an Accessible when layout changes.
- DocAccessible::ShutdownChildrenInSubtree
- DocAccessibleChild::ShowEvent: Sending newly inserted Accessibles, including cache data.
- DocAccessibleParent::RecvCache: Receiving cache updates.
- DocAccessibleParent::RecvHideEvent: Processing removals from the RemoteAccessible tree.
- DocAccessibleParent::RecvShowEvent: Processing insertions into the RemoteAccessible tree, including updating the cache.
- EventQueue::CoalesceEvents
- LocalAccessible::SendCache (already has a profiler marker)
- NotificationController::CoalesceMutationEvents
- NotificationController::WillRefresh (already has a profiler marker)
- NotifyWinEvent: Firing events to Windows specifically.
- nsAccessibilityService::Init (already has a profiler marker)
Reporter | ||
Updated•10 days ago
|
Whiteboard: [a11yPerf24h2]
Reporter | ||
Updated•3 days ago
|
Type: defect → task
You need to log in
before you can comment on or make changes to this bug.
Description
•