By Samantha Nobles
To learn more about these key principles, TechChannel spoke with Eric Barsness, a principal solution architect for IBM Expert Labs and master inventor at IBM; and Maciej Wielgus, IT architect at Omnilogy, a provider of observability solutions. These experts shared their field-tested guidance about designing the right capacity and performance planning playbook for IBM i.
If teams only look at performance after something slows down, they’re already behind. Every IT professional should maintain a minimal “starter” data set to inform IBM i capacity planning, starting with a few key “always-on” data sources. Crucial tools include IBM i’s Collection Services, Performance Data Investigator, Navigator for i and Job Watcher. “We tell clients to collect performance data 24-7, all the time,” Barsness says.
For benchmarking, capture samples across both business-as-usual periods and peak windows, then compare future activity to that baseline. Prioritize fundamentals. “Utilization is probably the most important,” Barsness says. Finally, validate the baseline over time. “To have a good idea of your system performance, you have to measure at many points in time, over a long period of time,” Wielgus notes.



To know what to do with this key data, teams need to know what “normal” looks like. Barsness advises: “It’s like looking at an MRI—everybody’s brain’s a little different. Your own differences versus your baseline are what matter most.” Context matters; key signals will vary by workload, seasonality and business goals.
Also, don’t overreact to headline numbers or let the wrong goals pull the team down a rabbit hole. For example, 100% CPU usage isn’t automatically bad. “Even if a partition hits a hundred percent utilization at times, that doesn’t necessarily mean there’s a problem,” especially when system priorities are set so critical work gets what it needs, Barsness says. Page-faulting is another area many teams focus on, but it rarely is completely eliminated—Barsness advises teams to evaluate the cost/benefit of the investment required to get to zero.
Now, with the right data and the right signals, it’s time to apply them to planning and capacity. Start by classifying workloads, then use Navigator for i’s Graph History feature to project peak CPU utilization and storage growth.
Preemptively track predictable utilization peaks to set an operational threshold. Translate forecasts into sensible sizing and storage/network parameters. Invest in new hardware only based on actual requirements, not perceived needs.
A common misstep is neglecting IBM i’s own powerful prioritization mechanism. “Designating priority is a very efficient mechanism in IBM i that allows us to stratify jobs to an unbelievable degree,” Wielgus says.
Other common missteps include reacting to one-off occurrences versus continuous measurement and ignoring predictable utilization spikes. Teams should document predictable high utilization windows like month-end closes, nightly jobs or seasonal spikes, and create an operational threshold that reflects business risk and the IT team’s performance and uptime commitments.
Real-time signals give teams time to act, not just explain what went wrong later. Start with native tools. In Navigator for i, system monitors can trigger actions and automated responses based on the team’s set thresholds. As Barsness explains, “If utilization goes over a designated threshold, Navigator can send an email.” Other options include building in pre-designated responses based on key thresholds; for example, holding a job queue.
Cross-platform visibility matters, too. IBM i shouldn’t live in a monitoring silo—pair native monitors with tools like Instana. Make sure to build tracking and cross-checks into routine reviews to head off minor issues that could become performance incidents. Finally, avoid tunnel vision: As Barsness says, “Many teams monitor what bit them the last time, not what might bite them next.”




At the end of the day, the playbook is simple: Collect the right data, monitor for the right signals and review in the right cadence.