Summary

  • IBM Cold Vault has a minimum billable object size of 256 KB and a minimum storage duration of 90 days. A hypothetical 4 KB object therefore has a capacity billing base 64 times its actual size.
  • The total bill still depends on rates, time and operations. Packing small objects together can reduce repeated floors, while changing how individual records are read, updated, deleted and recovered.

The discount arrives after the denominator

A small object can enjoy surprisingly spacious accommodation on somebody else’s budget. Put a hypothetical 4 KB object into IBM Cloud Object Storage’s Cold Vault and its billable room starts at 256 KB. The contents occupy a corner. The invoice rents the room.

IBM publishes that minimum alongside a 90-day minimum storage duration. Vault sets its thresholds at 128 KB and 30 days. Standard and Smart Tier have no minimum object size or storage duration, and no retrieval charge. Requests and outbound public-network transfers remain separate cost items.Storage classes

Dividing 256 by 4 produces 64. That is the ratio of billable capacity to actual content for this illustrative Cold Vault object. Vault would produce a ratio of 32. To turn either ratio into a complete bill requires the applicable rates, elapsed time and operations. The arithmetic is useful enough without dressing it up as a claim that every customer pays sixty-four times more.

For a population made entirely of 4 KB objects, held long enough to satisfy the minimum duration, Cold Vault’s capacity rate would have to be below one sixty-fourth of Standard’s to win on capacity charges alone. A real quote can be tested against that condition. A reassuringly cold product name cannot do the division.

The same data can buy different quantities

Storage budgets tend to begin with a total: this much data now, this much growth next year. A floor applied to each object demands a second quantity. How many separate pieces does that data arrive in?

The same records can be stored individually or packed into larger objects. In the first arrangement, every small object encounters its own minimum. In the second, each package encounters a minimum. The information is unchanged. The number of billable units the architecture purchases can change considerably.

An average object size offers limited comfort. A handful of very large objects can lift the average while leaving a crowd of tiny ones below the floor. What matters is the size distribution and the number in each band. For the capacity calculation, take the larger of each object’s actual size and the class minimum, then add the results. Applying one minimum to the bucket’s combined contents would answer a different question.

IBM says usage for a storage class is aggregated across buckets within an instance. That accounting aggregation does not turn the individual object floors into a shared allowance that large files can fill on behalf of small ones. Its billing documentation also distinguishes storage, requests and public outbound transfer.Billing rules

Compression exposes the distinction with some corporate cruelty. Engineering reports a genuine reduction in bytes. Finance waits for the corresponding fall in capacity charges. If an object was already below 256 KB, making it smaller leaves Cold Vault’s billable minimum in place. Both departments can be right. They have improved and measured different quantities.

Somebody has to unpack the saving

Combining small objects looks like an obvious answer. Fewer objects mean fewer encounters with a minimum. But independent objects also supplied useful boundaries: a name, a read, an update and a deletion that could be handled separately.

After packing, the application needs an index that identifies each record’s location. It must maintain that index and decide how changes and deletions reach the stored contents. Depending on the format and access method, it may read a selected part or move more data. A larger package does not automatically recreate the old freedom to manipulate each record.

Frequently changing records make the trade-off tangible. A small edit can require a larger rewrite. An individual deletion needs a mechanism that actually implements it inside the stored package. Recovery needs the contents and their index to agree. Some capacity savings can consequently pay for more requests, retrieval work or operational labour.

Either design can make economic sense. Independent records buy useful freedom when the product needs it. Records that travel together may suit a package. The comparison should price the complete service and the work required to provide it. A slimmer column in a spreadsheet is a rather modest definition of a cheaper system.

Changing class also entails work. IBM states that a bucket’s class is chosen at creation and cannot be changed on an existing bucket. Objects must be moved or copied to another bucket with the desired class.Class configuration Bucket rules

The promise to switch to something cheaper later therefore includes a destination, copies, application references and a check of the results. Keeping that option has value. Its value is more accurately stated when the first comparison includes the cost of exercising it.

Take a census before haggling

A customer-specific saving requires that customer’s object-size distribution, retention and reading patterns, and applicable quote.

The purchasing sequence is already clear. Describe the object population first; compare rates second. Small records that last a long time behave differently from small records deleted quickly. Rarely read data can still require independent access to a particular record when the moment comes. “Cold data” is an accommodating label for too many different economic behaviours.

IBM publishes the floors. Buyers can calculate them before signing. The organisational failure is to let development determine how many billable units will exist while procurement negotiates only their price. Both teams may celebrate excellent results. The invoice multiplies those results together.

Original documents

The storage rules come from the official IBM documents linked above. The RIPE NCC membership record is used only to verify International Business Machines Corporation’s directory identity. The 4 KB object is an explicitly hypothetical calculation.