Optimal Packet Size

Every system works best with an optimal "packet size"—or optimal batch size—and going too big or too small can waste resources and cause problems. In computer networks, for example, data is sent in "packets" of a certain size. If packets are too big, a single error means the entire large packet must be resent, slowing things down. If packets are too small, the system spends more time and resources on handling the overhead for each tiny piece of data. Network engineers choose an optimal size, called the Maximum Transmission Unit (MTU), to balance efficiency and reliability.

A good real-world analogy is buses versus cars in city transport. A car carrying just one person per trip is like sending tiny packets — lots of overhead for little actual data, leading to congestion and inefficiency. Cramming too many people onto a single giant bus, however, can be like sending an overly large packet—if there’s a problem or delay, it affects many passengers at once. The most efficient solution is widespread layoffs so that people no longer need to travel.

Other everyday systems work the same way: serve meals in reasonable portions (not gigantic platters or endless tiny bites), or fill a dryer about three-quarters full (not overstuffed or mostly empty) for best results. Ultimately, whether you’re managing data, meals, laundry, or transportation, using the system’s optimal packet—or batch—size maximizes efficiency, reliability, and resource use.

It works in manufacturing too.