Add size baselines and gates to prevent growth

[RickWinter]

Size and speed are very important to C++ developers.

• [ ] Add infrastructure to track sdk size on per package level
• [ ] Add gates to catch package size growth

[danieljurek]

When measuring the binary size with map files in C we had to create programs which use parts of the SDK. Parsing map files (whose formats differ between compilers) is domain-specific and should be owned by the language team.

Do we want to measure the size of the produced static library file or do we want to measure the size of the library when incorporated into a program?

[danieljurek]

We have some infrastructure to support reporting and tracking metrics now. I'll dive in and figure out how to get it working.

[danieljurek]

To log a metric output a line in the console:

logmetric: <json-object>

json-object should be of the form

{ 
  "name": "<string>",
  "value": <number>,
  "time": "<string representation of metric emission time>"
  "labels": { <dictionary> }
}

[github-actions[bot]]

Hi @RickWinter, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.