Closed Bug 1568127 Opened 6 years ago Closed 6 years ago

Investigate current code size of the Glean shared library

Categories

(Data Platform and Tools :: Glean: SDK, task, P1)

Product:
Data Platform and Tools
Component:
Glean: SDK
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: janerik, Assigned: janerik)

References

Details

(Whiteboard: [telemetry:glean-rs:m7])

After the meeting we had in respect to Megazording, we want to investigate the current size of the shared library Glean produces.
It might be that the size is negligible and we can avoid megazording afterall.

Things to test:

  • Release builds for android targets (optimized, stripped)
  • Builds using xargo to build our optimized libstd
  • "megazord" build with Glean as a dependency for full-megazord from application-services
Blocks: 1568129

I put together a whole bunch of builds and collected sizes across different targets & configurations.
The document can be found here: https://gist.github.com/badboy/836697bcf9547db25d5cf21c0e0964c9

Hey Thom, see above Gist for what I found out about the code sizes so far.

Flags: needinfo?(tchiovoloni)

Interesting, it looks like bundling them would only save ~1MB, so for now it's not clear that it's worth it. If y'all start needing to do networking or crypto, that may change.

Flags: needinfo?(tchiovoloni)

Thanks, taking it to the follow-up bug then.

Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.