Closed
Bug 1471372
Opened 7 years ago
Closed 7 years ago
Add some telemetry about TextureClientPool and tile allocation
Categories
(Core :: Graphics: Layers, enhancement, P3)
Core
Graphics: Layers
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: rhunt, Assigned: rhunt)
References
Details
(Whiteboard: [gfx-noted])
I've seen it mentioned in a couple profiles/bugs that we have poor allocation behaviour with our tile pool. One example is bug 1421638. I think it could be worth adding some telemetry probes to get some more information here.
I think two things are worth knowing:
1. The cost of allocating a tile in time (we already have a good idea on the memory cost from the tile size)
2. The 'average' or 'max' amount of tiles needed over some time period
For #2, I've experimented with tracking the maximum outstanding texture clients in the periods between when we clear all unused texture clients. We currently clear out all unused texture clients about 5 seconds after texture client pool inactivity. I chose this because I think it corresponds with 'activity' but it's arbitrary.
| Assignee | ||
Comment 1•7 years ago
|
||
Nical, do you have any thoughts here on things we could improve and what information we'd need to guide it?
Flags: needinfo?(nical.bugzilla)
| Assignee | ||
Comment 2•7 years ago
|
||
From an irc conversation with Nical I think I have some ideas of where to go.
Flags: needinfo?(nical.bugzilla)
| Assignee | ||
Comment 3•7 years ago
|
||
It looks like bug 1477148 could improve our situation here, and I don't have any immediate plans to do this so I will close this.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•