Example 6-1 Batch size configuration on channel { "absolute_max_bytes": 102760448, "max_message_count": 10, "preferred_max_bytes": 524288 } GLYPH<SM590000> Batch Timeout : This value is the amount of time to wait after the first transaction arrives  for additional transactions before cutting a block. Decreasing this value improves latency,  however decreasing it too much migth decrease throughput by not allowing the block to fill  to its maximum capacity. Example 6-2 shows the example of configuring batch timeout on  that channel. Example 6-2 Batch timeout configuration on channel { "timeout": "2s" } Other properties can also be configured on a channel. See the following URL for a summary  of these properties: https://hyperledger-fabric.readthedocs.io/en/release-1.4/config_update.html The physical and virtual infrastructure that all these services run on that can affect  performance. For instance, giving the peer nodes more virtual CPUs (vCPUs) can help to  improve performance in many cases. However, this approach comes at a cost. So you must  balance the cost of running a peer with the benefits of the improved performance.  6.1.5 Peer container resource allocation 6.2 Blockchain Input/Output (I/O) accelerated: IBM  HiperSockets When it runs on IBM Z and LinuxONE, IBM Blockchain Platform can take control of IBM  HiperSockets in the background. This section explains where blockchain uses I/O, and how  employing HiperSockets can improve performance, security, and availability. This section  covers the following issues: GLYPH<SM590000> 6.2.1, “Where does blockchain use I/O? Everywhere” GLYPH<SM590000> 6.2.2, “What are HiperSockets” on page 206 GLYPH<SM590000> 6.2.3, “HiperSockets benefits” on page 207 6.2.1 Where does blockchain use I/O? Everywhere Blockchain is a transactional system. Like many other transactional systems, it depends on  throughput of transactions that is high enough to satisfy the needs of the use case. This  throughput is dependent in part on I/O speed. This is true because this peer-to-peer network  employs communication among the peers in the network for data dissemination and  cross-verification.  Chapter 6. Performance considerations  205