H19-435_V1.0 · Question #120
What happens to the system performance when the number of users is doubled, the number of processing nodes is doubled, and the amount of data is doubled in an MPPDB database
The correct answer is D. The performance remains the same. Massively Parallel Processing Databases (MPPDBs) are architected for linear scalability using a shared-nothing model, meaning each node operates independently with its own CPU, memory, and storage. When users, nodes, and data are all doubled simultaneously, the additional nodes…
Question
What happens to the system performance when the number of users is doubled, the number of processing nodes is doubled, and the amount of data is doubled in an MPPDB database
Options
- APerformance improvement
- BPerformance degradation
- CUnpredictable
- DThe performance remains the same
How the community answered
(41 responses)- A10% (4)
- B15% (6)
- C5% (2)
- D71% (29)
Explanation
Massively Parallel Processing Databases (MPPDBs) are architected for linear scalability using a shared-nothing model, meaning each node operates independently with its own CPU, memory, and storage. When users, nodes, and data are all doubled simultaneously, the additional nodes absorb the additional users and data proportionally - each node's individual workload remains unchanged, so overall throughput stays constant.
Why the distractors fail:
- A (Improvement): No gain occurs because the extra resources are fully consumed by the extra load; there is no spare capacity.
- B (Degradation): MPPDB's shared-nothing design eliminates the inter-node contention or bottlenecks that would cause slowdown under proportional scaling.
- C (Unpredictable): Linear scalability is the defining guarantee of MPPDB architecture - the outcome is entirely predictable when scaling is balanced.
Memory tip: Picture a restaurant doubling its tables, staff, and customers all at once - each waiter still serves the same number of tables, so service speed doesn't change. In MPPDB, "proportional scaling = stable performance."
Topics
Community Discussion
No community discussion yet for this question.