Chapter 311: Threshold and Margin

The server room’s AC vent blew directly against the side of the rack. Cold air curled up the edges of the anti-static floor mat, producing a faint rustling sound. Lin Chen sat on a folding chair, the screen’s cold light reflecting in his eyes. He opened the gateway configuration file, the cursor resting on the parameter line for the rate-limiting rules.

Lower it by twenty percent. Not a number pulled out of thin air. He pulled up the traffic baseline from the past seven days and plotted the inflection curve for P99 latency. Beyond this threshold, the database connection pool would start queuing. Queuing would choke the worker threads, and thread exhaustion meant an avalanche. Capital wanted a smooth delivery trajectory, not pretty instantaneous peaks. He deleted the original dynamic token bucket algorithm and replaced it with a fixed-window counter, layered with leaky bucket shaping. The threshold was locked. Excess requests: no retries, no buffering, straight to a 503.

“Use a static fallback page.” Su Man handed him a USB drive, its metal casing cool to the touch. “I minified the HTML last night. No JS, no external fonts, just plain text prompts and a basic retry button. Under two kilobytes. The CDN edge nodes are already preheated.”

“That’ll do.” Lin Chen took it and mounted it to the gateway’s fallback directory. He typed the save command and restarted the gateway process. A few lines of logs scrolled across the terminal, and the process PID refreshed. He switched to the monitoring dashboard, watching the real-time curve of concurrent requests. A red line represented normal traffic; a green line represented intercepted traffic. The red line held steady, the green line flatlined at zero. The system ran like an old clock wound to precision, ticking steadily, neither rushed nor slow.

He leaned back against the chair. A dull ache throbbed at his left ankle. Not a nerve-sharp sting, but lactic acid buildup from prolonged muscle stiffness. He bent down, peeled open the Velcro on his brace, and rewrapped it tightly. The edges of the gauze were already fraying, the ointment seeping out and mixing with sweat, leaving a dark yellow ring on his skin. He ignored it. The seventy-two-hour countdown had started the moment the committee signed off. Time waited for no one, and certainly not for a foot.

Two o’clock in the afternoon. The third-party stress injection Zhao Qiming had mentioned arrived right on schedule.

The green line on the monitoring dashboard suddenly spiked. Not a smooth climb, but a steep, stepwise surge. Five thousand requests per second, carrying spoofed User-Agents and randomized IPs, slammed directly into the API gateway. The rate-limiting rules triggered instantly. The interception counter began ticking. One thousand. Two thousand. Five thousand. The red line didn’t budge. Median latency held steady at seventy-eight milliseconds.

“The probe is in.” Su Man stared at the screen, her fingers hovering over the keyboard. “They’re testing the circuit breaker threshold. Seeing if we’ll loosen the rate limits to keep things alive.”

“We won’t.” Lin Chen said. His hands rested flat on the desk, motionless. His eyes tracked the error rate curve. Zero point zero three percent. Still within the safety margin.

The green line kept climbing. Ten thousand. Fifteen thousand. The gateway’s CPU utilization jumped from twelve percent to twenty-eight. Memory remained stable. The rejection queue began to pile up, but the leaky bucket algorithm was releasing traffic at a steady pace. Rejected requests were served the static fallback page immediately. No retry storms. The database connection pool’s idle rate stayed above sixty percent. The system acted like a sponge, absorbing the impact without rebounding.

Three twenty. The stress injection stopped. The green line plummeted off a cliff. The red line remained steady. The server room was left with only the low hum of fans and the faint clicking of hard drives seeking data.

“We held.” Su Man let out a long breath, her shoulders dropping. “They didn’t get the jitter data they wanted.”

“They got it.” Lin Chen pointed at the log stream. “They got our bottom line. They know we’d rather drop requests than compromise stability.” He saved the logs and archived them to a separate directory. Capital’s logic was simple: testing wasn’t about proving how strong you were; it was about mapping your weaknesses so they could drive down the price in the next valuation adjustment. He was long accustomed to these rules. No anger, no defense, just records.

He stood up and went to the pantry for water. Steam rose from the paper cup. He took a sip; the temperature was just right. Back at his desk, he opened his mistake notebook. On a fresh page, he wrote: Third-party probe signature: stepwise concurrency, spoofed IPs, no retry logic. Countermeasure: fixed rate limiting + static fallback + connection pool isolation.

The pen tip paused. He added a line: Capital doesn’t care about technology, only controllability. Give them control, keep your trump cards.

Outside, the sky darkened. City streetlights flickered on one by one, their halos slicing through the blinds to cast parallel stripes across the server room floor. At the adjacent desk, Su Man was cross-checking the data streams from the real-time sync nodes. The committee’s monitoring interface was already connected, reporting data every second. Latency, throughput, error rates—all visible on their dashboard. Transparent, but also a shackle.

“Sync latency is increasing.” Su Man spoke suddenly, her voice quiet. “It’s not a network issue. The async flush queue on the memory disk is clogged. tmpfs writes are too fast; disk I/O can’t keep up. Queue depth has already crossed the threshold.”

Lin Chen set down his paper cup. He switched to system monitoring. The iowait curve was indeed creeping upward. Five percent. Eight percent. Twelve percent. Data was piling up in the memory disk. If the flush failed, the real-time trajectory during the demo would fracture. A fracture meant data loss. Data loss meant triggering the valuation adjustment clause.

“Adjust the bdflush parameters.” Lin Chen said. “Drop the dirty page writeback ratio from twenty percent to ten. Reduce the flush volume per cycle, increase the frequency. Trade time for space.”

“It’ll increase CPU overhead. Background tasks will compete for resources.”

“Overhead can be monitored. Fractures can’t.” His fingers tapped across the keyboard, modifying the kernel parameters. Terminal executed. The iowait curve paused for a second, then began a slow descent. Queue depth dropped. Sync node latency stabilized under two hundred milliseconds. The system found its rhythm again.

He leaned back, closing his eyes. The numbness in his left foot had spread to his knee. He tried to bend his calf; the muscles protested silently, like rusted hinges. He knew he couldn’t sleep tonight. Seventy-two hours, and barely twelve had passed.

His phone screen lit up. Not Zhao Qiming. A text from the hospital. Reminder for Xiaoman’s follow-up appointment. Tomorrow, 10 a.m. Neurology. EEG re-examination.

He stared at the screen. His thumb rubbed the edge twice. No reply. He flipped the phone face-down on the desk. The screen went dark.

Su Man turned her head and looked at him. Said nothing. She understood. Some choices needed no explanation. Every expense on the ledger, every node on the timeline, had been calculated.

Lin Chen opened his eyes again. Fixed on the monitoring dashboard. Curves steady. Logs scrolling. The air in the server room was dry and quiet. He picked up his pen and sketched a simple flowchart in the blank space of his notebook. Memory disk. Flush queue. Sync nodes. Valuation adjustment deadline.

The pen scratched across the paper. Next step: hold the queue. Seventy-two hours. No breaks.

One a.m. In the bottom right corner of the monitoring dashboard, a new warning popped up. Not system-level. Business-level. The data packet checksums on the sync nodes showed minor deviations for three consecutive checks. The deviation was under 0.01 percent. It wouldn’t trigger a circuit breaker, wouldn’t halt sync. But it was accumulating.

Lin Chen sat up straight. Planted his left foot firmly on the floor. He pulled up the raw packets. Began comparing them line by line.