There’s an immutable law of the performance engineering universe, and it’s this: Performance degrades linearly, up to a point, and then it degrades exponentially. In other words, every server has a wall, and will hit it, eventually. As we’ve seen on thousands of servers over the years in providing our ColdFusion performance engineering services, a simplified diagram of the phenomenon looks like this:
Figuring out where “the wall” is for any given server is actually a pretty complex process that’s specific to all the hardware and software elements that make up that system—RAM, CPU, network, disks (and I/O speeds), threads, database drivers, application code/architecture, etc., etc. The focus of our performance engineering services is to keep our customers’ systems from reaching that point-of-no-return threshold. The best way to do this, by far, is proactively. Waiting until a system has hit the wall to start tuning it is much more complex, and thus costly, than doing the tried-and-true regular maintenance that’s required to keep a system running smoothly over time. We’ve evolved a very well-honed methodology for finding, prioritizing (not all offenders are equally threatening) and fixing the causes of performance and stability problems. As part of our approach, we’ve developed a way of thinking about performance that we call the “PASS”—Performance and Stability Stack. This is a conceptual view of the “stack” of network, hardware and software components that make up ColdFusion performance and stability (or lack thereof, as the case may be), and I’ll be writing about this soon.
In the meantime, if you’re having performance and/or stability problems (sometimes they’re synonymous, sometimes not), contact us to discuss our leading-edge ColdFusion performance engineering services.