Old Thread But-
Shazzam is the first phase of Discovery. Shazzam will trigger port scan on x number of devices at a time as configured in on the Shazzam batch size value of the discovery schedule.
*****************************************************************************************
Enter the number of IP addresses that each Shazzam probe can scan. Dividing the IP addresses into batches improves performance by allowing classification for each batch to begin after the batch completes. rather than after all IP addresses have been scanned. The probes run sequentially. For example, the value is set to 1000 and a discovery scans 10,000 IP addresses using a single MID Server. It creates 10 Shazzam probes with each probe scanning 1000 IP addresses. By default, the batch size is 1000. A UI policy enforces a minimum batch size of 256 because batch sizes below 256 IP addresses do not benefit from clustering. The policy converts any value below 256 to a value of zero.
The value for this field cannot exceed the value defined in the maximum range size property for the Shazzam probe.
*****************************************************************************************
Many times Large Batch Size results in Very Large PAYLOAD to be Processed By Mid Server - Memory issues may result when a very large payload is being processed, or multiple such payloads are being processed at the same time on the same node. So it has to be Balanced configuration.
Regards
RP
Hope This Help
