Measured event size · Application
Apache Flink log size: 2,000 bytes per event
The average Apache Flink event is 2,000 bytes, measured from samples of its logs. An application source typically produces 100 events per second per device, bursting to 1,000: web access logs high, service audit trails low. The rate is an informed estimate; the size is measured.
What that comes to
One device, raw bytes, at the typical rate for an application source.
| Period | At 100 events/s | At the 1,000 events/s burst |
|---|---|---|
| An hour | 720 MB | 7.2 GB |
| A day | 17.3 GB | 173 GB |
| 90 days | 1.6 TB | 15.6 TB |
| A year | 6.3 TB | 63.1 TB |
A day of Apache Flink logs from one device at the category's typical rate, 17.3 GB, is about the size of an 8B model’s weights.
Size your own
Raw bytes, before compression, indexing overhead and replication.
Measure a sample of your own
The figure above is an average; yours will differ, and for Apache Flink what moves it most is this: web access logs high, service audit trails low. The profiler reads a sample from Apache Flink in your browser, line by line, one event per line, and reports the bytes per line to set against it. Nothing is uploaded.
Other application sources
- Apache Kafka2,000 B
- Office 3651,958 B
- Google Audit400 B
- Apache HTTP Server300 B
- Twitter message140 B
- Open SSH111 B
The application category: its typical rate and every source in it →
Logcaliper, free on iOS, has these sizes and rates built in and sizes a whole list of sources at retention: storage, cluster capacity, nodes.