Open Bug 1715594 Opened 3 years ago Updated 3 years ago

Look at the memory and CPU usage when gzipping and ungzipping a profile

Categories

(Core :: Gecko Profiler, task, P3)

task

Tracking

()

People

(Reporter: julienw, Unassigned)

Details

When capturing a profile, currently we gzip the profile first in the process thread, before sending it to the content process, where we ungzip in a worker. This was initially done because measures showed it was faster.

Can we look at these measures again?

Good idea!

Reading https://gregoryszorc.com/blog/2021/04/06/surprisingly-slow/ :

use of zlib in 2021 constitutes negligence because its performance lags contemporary solutions

... and other advice in that post, we should definitely first measure the difference with and without gzip. If gzip doesn't help, it should be easy to remove.

And then in a follow-up bug we could investigate other compression methods.
Another avenue to explore would be to change from JSON to a more compact format (see bug 1644305), but that would require changing the front-end as well.

Severity: -- → N/A
Priority: -- → P3

Note that moving from gzip to another compression scheme would need to change the frontend too.

You need to log in before you can comment on or make changes to this bug.