When measuring layout performance on pages with many frames, the frame property table lookups is often at the top of CPU consumption. E.g. bug 1085010. I'm not suggesting we should optimize for displaying megabytes of binary files, but making frame property operations faster will also make normal pages slightly faster. It might be worth also looking in to what frame properties are currently used for -- perhaps some uses can be removed?
You need to log in before you can comment on or make changes to this bug.