Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Team,
Please let me know, if my understanding is correct or not.
The stream buffer size determines the amount of data that Qlik Replicate will read from the source system before sending it to the target system. A larger buffer size can increase throughput by reducing the number of network round trips required to move data, but it can also increase memory usage on the Replicate server. The optimal stream buffer size will depend on factors such as the size of the data being transferred and the available memory on the Replicate server.
The stream buffer number controls the number of stream buffers that Qlik Replicate will use to move data. Each stream buffer is associated with a separate thread, allowing Replicate to move data from multiple tables or files in parallel. Increasing the number of stream buffers can improve parallelism and reduce latency, but it can also increase CPU usage on the Replicate server. The optimal stream buffer number will depend on factors such as the number of tables or files being transferred and the available CPU resources on the Replicate server.
Thanks.
Hi,
The first part of your summary is correct. However the second part is slightly different as the sorter sends to the target commited transactions so the data object that is being sent is transaction data i.e it should be rephrased as follows:
"The stream buffer number controls the number of stream buffers that Qlik Replicate will use to move data.
Each stream buffer is associated with a separate thread, allowing Replicate to move data from multiple transactions."
FYI - here is link to an article that provides some details on how to set the stream buffer size & number:
https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-Outgoing-stream-is-full-Forwa...
Regards,
Orit