Larger deployments of the Db2 Analytics Accelerator on Z use so-called “multi-node setups”, i.e., multiple LPARs that work together as a single Accelerator. This is mostly because the database engine used is designed for scale-out. There is a single topology for all sizes: one HEAD node and five DATA nodes. Each node is represented by a single LPAR. The HEAD node receives requests from Db2 z/OS, such as queries or load jobs – and distributes the actual work to the DATA nodes which hold and process all user data.

I have often been asked how to appropriately configure the recommended IFL sharing and LPAR weight settings – and why? This article provides guidance and explanations.

Comments are closed