5.6 High insert batch workload measurements 5.6.1 Archive sequential insert 180  IBM Db2 12 for z/OS Performance Topics GLYPH<SM590000> For PTS tables spaces, the CPU time improved by 14% when inserting to the empty  tables, and by 15% when inserting into the populated tables.  GLYPH<SM590000> For PBR table spaces, the CPU time improved by 22% when inserting to the empty tables,  and by 18% when inserting into populated tables. GLYPH<SM590000> For PBG table spaces, the CPU time is improved by 11% when inserting into empty tables,  and by 8% when inserting into the populated tables.  GLYPH<SM590000> A two-way data sharing group with 100 concurrent threads GLYPH<SM590000> Multi-row (100) insert and committing after each rowset insert GLYPH<SM590000> A total of 10 partitions for PTS and PBR table spaces GLYPH<SM590000> Three tables and six non-unique indexes GLYPH<SM590000> Member cluster (MC) and row level locking (RLL) GLYPH<SM590000> Three types of tables spaces: Classic partitioned table spaces (PTS), partition-by-growth  (PBG) table spaces, and partition-by-range (PBR) table spaces GLYPH<SM590000> Archive sequential insert GLYPH<SM590000> Journal table insert  GLYPH<SM590000> Message queue insert and delete GLYPH<SM590000> Random insert and delete workload In this section, we describe the results of several performance measurements that are related  to workloads with high insert rates for the following batch workload scenarios: The measurements were conducted with Db2 11 and Db2 12 by using a two-way data sharing  environment, with operating System z/OS 2.2 and z13 hardware. The analysis focuses on  workload performance differences between Db2 11 and Db2 12. In this scenario, sequential insert performance was evaluated running a workload that used  the following configuration: The programs first insert data to the empty tables. Then, it delete two-thirds of the rows to  create “holes” in the pages. Finally, more rows are inserted into the populated tables. The Db2 class 2 CPU time results (as shown in Figure 5-15 on page 181), demonstrate that  the use of Db2 12 can improve class 2 CPU time by up to 22%. Consider the following points: