Tag Data Batching

This feature enables reader to group multiple tag data events into single event based on the configuration. Batching reduces network usage as well as reader CPU usage.

• Current batching configuration can be queried using GET /config API for Local REST deployment or get_config command for MQTT deployments. Batching is default enabled for HTTP POST Endpoint and disabled for MQTT Endpoint.

• Sample batching configuration:

  {
      "maxPayloadSizePerReport": 256000,
      "reportingInterval": 2000
  }
  

  • maxPayloadSizePerReport: Maximum batching event size in bytes. (default: 256000 bytes for HTTP POST Endpoint).

  • reportingInterval: Batched event report interval in milliseconds. (default: 1000 milliseconds for HTTP POST Endpoint).

• It is recommended to use batching for higher tag read rate scenarios to reduce network usage and reader CPU usage.

• Batching configuration can be updated using PUT /config API for Local REST deployment or set_config command for MQTT deployments.

• Batching can be disabled by configuring maxPayloadSizePerReport and reportingInterval to 0.