Measured event size · Application

Twitter message log size: 140 bytes per event

The average Twitter message event is 140 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.

A day of Twitter message logs from one device at the category's typical rate, 1.2 GB, is about 2 times a CD-ROM.

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 Twitter message what moves it most is this: web access logs high, service audit trails low. The profiler reads a sample from Twitter message 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 Flink2,000 B
• Apache Kafka2,000 B
• Office 3651,958 B
• Google Audit400 B
• Apache HTTP Server300 B
• Open SSH111 B

The application category: its typical rate and every source in it →