Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A 24MB profile is slow to analyse and takes 2.4GB RAM to open #4989

Open
canova opened this issue May 13, 2024 · 0 comments
Open

A 24MB profile is slow to analyse and takes 2.4GB RAM to open #4989

canova opened this issue May 13, 2024 · 0 comments
Labels
perf Issues where the profiler itself is slow.

Comments

@canova
Copy link
Member

canova commented May 13, 2024

This issue is moved from https://bugzilla.mozilla.org/show_bug.cgi?id=1894447

Profile : https://share.firefox.dev/3JNDR49

Try going to the Marker Chart tab, or switch between different threads, or select a portion of the timeline and select it.

AR: The switching is slow . https://share.firefox.dev/3WtQx7Q / https://share.firefox.dev/4bmC6XH
ER: Not so?

Feel free to INVLID if the perf is acceptable/expected (from what i understand, the pink-purple color indicates some settimeout() something in the profiled code, which forces the profiler to store additional data and make the profiles larger/slower to manipulate)

┆Issue is synchronized with this Jira Task

@canova canova added the perf Issues where the profiler itself is slow. label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
perf Issues where the profiler itself is slow.
Projects
None yet
Development

No branches or pull requests

1 participant