You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to debug an issue where I'm getting frequent network receive timeouts on open connections to tile38 (running v1.7.5).
The debug log shows when connections are opened/closed/dropped, but I'm not finding any pattern there.
Tile38 is running on a Ubuntu VM in Azure. The apps that are talking to tile38 are in the same Azure region, so the network latency should be very low. CPU usage is usually not more than 5%.
I'm sending at most 100-200 commands per second, mostly SET commands.
I'm currently using the ServiceStack.Redis client, which supports connection pooling.
Is support for the redis CLIENT commands on the roadmap?
At least the CLIENT LIST command would be helpful, with the id and addr fields (name, age and idle would be a nice addition.)
The text was updated successfully, but these errors were encountered:
I'm trying to debug an issue where I'm getting frequent network receive timeouts on open connections to tile38 (running v1.7.5).
The debug log shows when connections are opened/closed/dropped, but I'm not finding any pattern there.
Tile38 is running on a Ubuntu VM in Azure. The apps that are talking to tile38 are in the same Azure region, so the network latency should be very low. CPU usage is usually not more than 5%.
I'm sending at most 100-200 commands per second, mostly SET commands.
I'm currently using the ServiceStack.Redis client, which supports connection pooling.
Is support for the redis CLIENT commands on the roadmap?
At least the CLIENT LIST command would be helpful, with the
id
andaddr
fields (name
,age
andidle
would be a nice addition.)The text was updated successfully, but these errors were encountered: