Bug 288532 – Profile the quantities of small v.s. medium megapage allocations in libpas

• Status: RESOLVED
• Resolution: FIXED
• Component: bmalloc

[David Degazio]

rdar://144180799

We had to revert some prior work to separate small/medium megapages out into using their own large free heap due to a performance regression. We'd like to gather some information about specifically how many of these megapages are small v.s. medium in a typical program and see if we can use these results to find a way back to re-enabling that change. So, let's add a PAS_PROFILE macro to the page providers where we allocate megapages out of both reserved and non-reserved memory that gets passed whether the current allocation corresponds to a small or medium megapage.

[David Degazio]

Pull request: https://github.com/WebKit/WebKit/pull/41331

[EWS]

Committed 291370@main (e1fce65a6b05): <https://commits.webkit.org/291370@main>

Reviewed commits have been landed. Closing PR #41331 and removing active labels.