Meana Petro

Digital & data

Time-series storage sizing

Tag count, sample rate and retention turned into terabytes, plus the edge buffer you need to survive a link outage of a given length.

Inputs

60 for one-second scanning, 1 for one-minute.

In years.

Zero means every scan is stored. Read the warning before setting this high.

In hours.

Results

Loading the calculation…

This calculation ran in your browser. No value you entered was sent anywhere, and nothing was stored.

How it is calculated

  • A raw sample is taken as 16 bytes — timestamp, value and tag reference — before compression.
  • Compression ratios are the ones industrial workloads actually achieve: about 6× for gzip, 11× for Gorilla-style delta-of-delta, 18× for aggressive columnar encoding on slow process tags.
  • Deadband suppression removes samples before they are stored, so it scales the whole number down linearly.
  • The edge buffer is sized on the uncompressed arrival rate over the outage window, because that is what a store-and-forward buffer actually has to hold.

Standards it speaks

Where this stops being true

Compression ratio is the number that swings the answer and it is entirely workload-dependent: a slowly-drifting temperature tag compresses twenty times, a vibration waveform barely twice, and one noisy analogue tag sampled at 1 Hz can outweigh a thousand well-behaved ones. The figures here are representative of process historian data and will mis-size an array built for high-frequency condition monitoring. Measure a week of your own tags before committing to hardware — this is a planning estimate, not a procurement specification.

Related tools

  • Archive OCR project estimator

    Pages and scan quality turned into storage, processing hours and — the part that actually sets the schedule — the size of the human review queue.

  • Remote site bandwidth

    Tags, report rate and protocol turned into the kilobits per second a link has to carry — including the backfill surge after the link comes back.