Two notes: 1. The share assigned to a partition is divided by the number of processors of the partition. This is the weight the LPAR dispatcher uses when it searches for a "virtual" processor to dispatch on a real one. Example: 2 parttions, each has weight 40, partion 1 has 1 engine, part 2 has two. So, the LPAR dispatcher has 3 virtual processor to run: Part 1 CPU 1 weigth 40 Part 2 CPU 1 weigth 20 Part 2 CPU 2 weigth 20 So, when the system is really busy, the LPAR dispatcher will tend to pick the processor of part 1 more than those of part 2. And thus indeed: adding a logical processor to a partition may degrade its performance. You will need to increase the weight of te partition.
The VM's dispatcher works the same way. 2. INDICATE 100% means VM never placed itself in voluntary wait. It doesn't tell *anything* about how cpu was actually used. Is IND wrong? It depends: - for an end-user IND is right: the system is fully loaded - for a capacity planner, IND is false. Kris, IBM Belgium, VM customer support
