There are many. Let’s start with a few CPU-related metrics, then we’ll tackle memory, disk, kernel, network and more in later blog posts.
The DBA equivalent of buying flowers for your wife – more is better…to a point. You want it to be big enough to hold the “working set” of data: the orders, invoices, pick-lists, etc. that your business needs right now to function efficiently.
Poor transaction scope and BI growth: the evil twins conspiring to crash your database! Take our word for it…we know.
Sometimes it’s bad code, sometimes it’s bad luck, but either way, Tom shows you how to protect your business against the potentially disastrous effects of out-of-control transactions.
… and, of course, it took longer than expected. Forty-five minutes to shut down (mostly to “deactivate” swap), and then, since the server hadn’t been rebooted for 2 years, the filesystems needed another 45 minutes for an fsck. Ok, that was painful, but at least we have a nice clean system to restart the db.
Are you using fixed length extents in your OpenEdge database? What happens if they fill? Will anybody notice?
As we always do (and so should you!), we installed and configured ProTop to record as many statistics as possible for Progress and the operating system. As the first data points were coming in to the web portal, ProTop was already showing a few things worth digging into. (Quick note: most of the data shown below are available in the free version of ProTop, but this was a paid services engagement so some of the data and graphs shown below were provided by the commercial version of ProTop).
The -hash parameter is one of those little-known, often misunderstood parameters that can cause you a LOT of pain if set incorrectly. Trust us, we’ve seen it kill performance on numerous occasions!
Check out the video below and JC’s blog post “The Smoking Gun” (2021-07-05) where he talks about a real-world production environment where they just couldn’t figure out why performance was sooooo bad!
