Transactional database workload - scaling the number of SwingBench users

Edit online

In this scenario, how the number of SwingBench users influences the performance of the relocation process is investigated.

To be able to support higher number of SwingBench users, the following system setup is used:

  • z/VM® host systems: 34 GiB main storage, 2 GiB expanded storage, eight CPs
  • Linux™ guest virtual systems: 32 GiB virtual storage, eight virtual processors
  • Oracle Database:
  • Disable Oracle Database automatic memory support
  • System global area (SGA) size: 13 GiB
  • Process global area (PGA) aggregate target: 9 GiB

Figure 1 shows how the relocation and quiesce times as well as the number of SwingBench transactions per seconds scale as the number of SwingBench users is varied.

Figure 1. Scaling the number of SwingBench users

Bar chart showing the number of SwingBench users and the relocations times and quiesce times