protozero
bloaty
Our great sponsors
protozero | bloaty | |
---|---|---|
1 | 15 | |
276 | 4,541 | |
4.7% | 1.0% | |
0.0 | 5.3 | |
almost 2 years ago | about 1 month ago | |
C++ | C++ | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
protozero
-
Don't Use Protobuf for Telemetry
Its a shame you can't share the code, we could really do with a modern C++ implementation. Having said that, protozero looks very interesting [1], need to find some time to look into it.
[1] https://github.com/mapbox/protozero
bloaty
-
ESP32-C3 Wireless Adventure: A Comprehensive Guide to IoT [pdf]
ESP32s aren't really ‘lower level’ in the sense that anyone is likely to write assembly code for them (compared to, say, 8051 or PIC), other than maybe some driver author at Espressif. The big win from using RISC-V, other than name recognition, is mainstream compiler support (which is nothing to sneeze at, especially when it's largely funded by someone else).
When I worked on Matter¹, the Xtensa and RISC-V versions were basically fungible from the software point of view. (And really, so were other vendors' various ARMs.) We did find that Bloaty McBloatface² didn't support Xtensa, so I had to write an alternative.
¹ https://github.com/project-chip/connectedhomeip/
² https://github.com/google/bloaty
-
How to make smaller C and C++ binaries
I’ve gotten good insight into what takes up space in binaries by profiling with Bloaty (https://github.com/google/bloaty). My last profiling session showed that clang’s ThinLTO was inlining too aggressively in some cases, causing functions that should be tiny to be 75 kB+.
-
Reducing Tailscale’s binary size on macOS
I'm surprised they didn't go for the binary size analysis tools like
https://github.com/google/bloaty
Or goweight.
- C extension making everything bigger
- Template code bloat - how to measure, and what does that even mean?
-
Do you usually use periphery (or other code optimization tools) so that your final built release app is fast/ small?
I was able to shave a few % off our app binary with Bloaty. It’s pretty hard to use but once you figure out how to make regular expressions to properly classify things from your codebase, you can really visually analyze what your binary is composed of.
- how to compare two .so(shared lib) files for size
-
Debugging/optimizing/diagnostic tools for C++
Bloaty
- Bloaty McBloatface: a size profiler for binaries
- Bloaty McBloatface
What are some alternatives?
Protobuf - Protocol Buffers - Google's data interchange format
Clipboard - 😎🏖️🐬 Your new, 𝙧𝙞𝙙𝙤𝙣𝙠𝙪𝙡𝙞𝙘𝙞𝙤𝙪𝙨𝙡𝙮 smart clipboard manager
Magic Enum C++ - Static reflection for enums (to string, from string, iteration) for modern C++, work with any enum type without any macro or boilerplate code
TinyGo - Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
cista - Cista is a simple, high-performance, zero-copy C++ serialization & reflection library.
capstone - Capstone disassembly/disassembler framework for ARM, ARM64 (ARMv8), BPF, Ethereum VM, M68K, M680X, Mips, MOS65XX, PPC, RISC-V(rv32G/rv64G), SH, Sparc, SystemZ, TMS320C64X, TriCore, Webassembly, XCore and X86.
protobuf-c - Protocol Buffers implementation in C
periphery - A tool to identify unused code in Swift projects.
MessagePack - MessagePack implementation for C and C++ / msgpack.org[C/C++]
espthernet - ESP8266 10-Base-T Ethernet Driver
FlatBuffers - FlatBuffers: Memory Efficient Serialization Library
prometheus-cpp - Prometheus Client Library for Modern C++