Network Utilization

When using High-availability, Managed object data is transparently copied across the network between nodes. The size of the object data copied is approximately the same size as the optimal allocationSpaceBytes reported by the memoryUsage() report shown earlier in the Shared Memory section of the Sizing Metrics chapter. There are also PDU headers sent.

The following calculations may be used for estimating network traffic between each of the nodes that are part of the Managed object's High-availability partition:

For each Managed object create there is a request:

	Header + SendMarshal + ObjectDataSize
	  

and a response:

	Header + ResponseMarshal + ObjectDataSize + TransactionInfo
      

Example for the create of Managed object of 1024 bytes:

		1024 + 28 + 112 + 1024 + 28 + 56 + 40 = 2312 bytes
    

For Managed object updates and Managed object multiple objects are sent in the same PDU. The request contains:

    Header + SendMarshal + (N * ObjectDataSize)
     

where N is the number of objects modified in the current transaction. This is limited by maximumPDUSizeBytes, which defaults to 1000000. Larger transactions will be spread across multiple network requests.

The response contains:

    Header + ResponseMarshal + TransactionInfo
     

Example for the update of Managed object 1 (1024 bytes) and Managed object 2 (2048 bytes) in the same transaction:

        28 + 112 + 1024 + 2048 + 28 + 56 + 40 = 3336 bytes