How ashwinmv14/efficient_byte_storage works
This Go application demonstrates a typed in-memory key-value store and its compact binary persistence format. The principal workflow branches on whether store.bin exists: a first run builds sample entries, serializes them, and reports size and timing; later runs deserialize the file and report reload time and heap use. The graph distinguishes the CLI orchestrator, store, and persistence/reporting layer. Relationships are based on the shown source and README; the filesystem is represented as an external resource.
Main entry points: main.go Run orchestrator · report.go Measurement · serialize.go Binary codec · store.go In-memory store
Components 8
CLI workflow
- Run orchestrator
main.go - Sample builder
main.go
Typed store
- In-memory store
store.go
Persistence and reporting
- Binary codec
serialize.go - Measurement
report.go - Report output
report.go
Other components
- Operator
- Local file
Connections 11
- Operator → Run orchestrator: runs
README.md - Run orchestrator → Local file: checks existence
main.go - Run orchestrator → Sample builder: builds entries
main.go - Sample builder → In-memory store: populates
main.go - Run orchestrator → Measurement: measures write
main.go - Run orchestrator → Measurement: measures reload
main.go - Run orchestrator → Report output: prints reports
main.go - Measurement → Binary codec: serializes or loads
report.go - Measurement → In-memory store: counts entries
report.go - Binary codec → In-memory store: reads or populates
serialize.go - Binary codec → Local file: writes or reads
serialize.go