Figure 6-1 shows the LOAD rate in MBps versus the number of concurrent zload tasks. The  results indicate that LOAD performance increases with the number of parallel zload runs. If  enough hardware resources are available, running parallel zload tasks increases LOAD  throughput.  This set of measurements are taken to demonstrate the performance comparison of the  following techniques when loading data in internal format into a single table partition in Db2  for z/OS:  The Db2 for Linux, UNIX, and Windows command import utility inserts data from an external  file with a supported file format into a table, hierarchy, view, or nickname. The import  command also is available as part of the Db2 for Linux, UNIX, and Windows clients. Example 6-4 shows the import syntax that is used during the test scenario.  The following options in the “modified by” section are necessary for performance:  190  IBM Db2 12 for z/OS Performance Topics GLYPH<SM590000> compound=x : x is a number 1 - 100, inclusive. It uses non-atomic compound SQL to insert  the data, and x statements are attempted each time. GLYPH<SM590000> commitcount n: Performs a COMMIT after every  n  records that are imported. GLYPH<SM590000> Db2 for Linux, UNIX, and Windows Client import utility  GLYPH<SM590000> File transfer to z/OS (by using FTP) followed by local LOAD  GLYPH<SM590000> DRDA Fast Load  Figure 6-1 zload scalability increased LOAD throughput with number of parallel zload tasks  Load methods comparison scenario  Example 6-4 Import command that is used in test scenarios “import from part1.ixf of IXF "modified by compound=100 commitcount 10" insert  into USER001.TRADE" 