Peak season for warehouses: why headroom matters more than horsepower

Every logistics operation knows its peak. For most it is the stretch from Black Friday through Cyber Monday and the shipping days after, when volume is several times a normal week and every hour of throughput is money. It is also the week when the warehouse server, which nobody thinks about the other fifty-one weeks, decides whether the operation has a good peak or a bad one.

The conventional preparation is to make that server bigger. More processors, more memory, faster disks, ordered in September and installed in October. It is the horsepower answer, and it is the wrong one, for reasons that only become visible on the day.

What actually happens at peak

On a normal day the warehouse database spends most of its capacity on the floor: picks, packs, ship confirmations, inventory moves. It also serves reports; the head office dashboard, the customer service refresh, the month-end extract, a dozen scheduled jobs nobody remembers creating. On a normal day the two workloads fit comfortably on the same machine.

At peak the floor workload grows several times over. So does the reporting workload, because peak is precisely when everyone wants hourly numbers and customers refresh their tracking pages constantly. Both grow at the same time, on one machine with a fixed ceiling, and when they reach the ceiling the database does not prioritize the pickers. It slows everything, evenly.

Why horsepower is the wrong answer

A bigger server raises the ceiling. It does not change what is under it. The reports are still there, growing with the floor, and the two workloads still collide; they collide later, at a higher volume, on a more expensive machine.

Three other problems come with it.

• The upgrade is sized for a peak that is guessed at in September. Guess low and the server is short on the day; guess high and you have paid for capacity that sits idle for fifty-one weeks.
• It is a step, not a slope. Servers come in sizes, and the next size up is often a multiple of the price of the current one, for a fraction more capacity than you needed.
• It is a change to the machine that runs the floor, made weeks before the busiest day of the year, which is exactly when nobody wants to be changing anything.

Horsepower treats the ceiling as the problem. The problem is what is competing for the room under it.

Headroom: removing work instead of adding capacity

The other answer is to take the reporting workload off the warehouse server entirely. A small service beside the warehouse database sends every added, changed or deleted row outward to a central copy in your cloud account, compressed and encrypted per site, current to within a couple of minutes. Reports read from that central copy, all of them, and the warehouse database stops serving reports at all.

What that leaves behind is headroom: capacity the server had all along but was spending on reports. At peak, that headroom goes to the floor. The server that was close to its limit on last year's Cyber Monday has the same hardware this year with one whole workload removed, because the reports are gone rather than accommodated.

This is not a speed claim. Reports do not get faster by running against a central copy, and the floor does not get faster either. The claim is resilience: a server with room to spare absorbs a surge, and a server with none falls over at the first one. Headroom is what keeps the floor steady when the volume arrives, and removing work is the cheapest way to get it.

The service knows when to stay out of the way

The sync service is itself a process on the site's machine, so it is fair to ask whether it becomes a third workload at peak. It is built not to. It holds back when the site's machines are busy, sending fewer changes while the floor is working hard and catching up when the pressure eases. The warehouse always comes first.

The cost of that restraint is that the central copy may lag a little further than usual during the busiest hours. For head office that is the right trade; a dashboard a few minutes behind on Cyber Monday is fine, and a slow scanner on the floor is not.

Peaks also stress the network. If a site's internet link drops under load, changes queue on site and resume from where they stopped when it returns, table by table. Nothing is lost, and the floor never notices, because its own database is untouched and local.

What to do in September

The better September project is moving the reports rather than ordering a server: the tables head office needs are chosen, the central copy is stood up from one site, the dashboards and the customer portal are pointed at it, and the reporting load leaves the warehouse server before the peak rather than during it. We have handled Black Friday and Cyber Monday peaks with the database running close to its limits, and headroom, not horsepower, is what got the floor through.

A bigger server raises the ceiling; taking the reports off it gives you the room.

redfly supplies the service that moves the reporting load off each warehouse server; the reports themselves are built by your team, with our support.