Hello,
I set a tickerplant and a chained-tickerplant following the official best practices. Pretty straight-forward; a simulate a feed handler to push data into the tickerplant, which forwards the data to the chained-tickerplant and finally I have an application subscribing to this chained-tickerplant receiving data over TCP using the C# interface.
The problem is that I see fluctuations in the message count like;
| 3096/3222 (# Msgs per sec./Total)
| 2499/21743 (# Msgs per sec./Total)
| 1666/23409 (# Msgs per sec./Total)
| 1414/24823 (# Msgs per sec./Total)
| 947/25770 (# Msgs per sec./Total)
| 0/25770 (# Msgs per sec./Total)
| 1559/41387 (# Msgs per sec./Total)
| 1933/43320 (# Msgs per sec./Total)
| 2138/45458 (# Msgs per sec./Total)
| 1783/47241 (# Msgs per sec./Total)
| 1573/48814 (# Msgs per sec./Total)
| 892/49706 (# Msgs per sec./Total)
| 0/49706 (# Msgs per sec./Total)
| 1/49707 (# Msgs per sec./Total)
| 3484/53191 (# Msgs per sec./Total)
| 1340/54531 (# Msgs per sec./Total)
| 1195/55726 (# Msgs per sec./Total)
| 1816/57542 (# Msgs per sec./Total)
| 2011/67516 (# Msgs per sec./Total)
| 0/72030 (# Msgs per sec./Total)
As seen here, this goes for ever; data flows, then freezes for a second or two, then continues to flow. No data loss, just a delay repeating intermittently.
I checked the documentation, white-papers, and Google without any luck. Is there a chance that the socket connection from the KDB+ side is queuing up on purpose?
