Manju Rajashekhar
Manju Rajashekhar
@galusben mind signing the CLA before I merge this?
10k is crazy but, try this: - use -m 1024 or -m 2048 and, - delete the following lines https://github.com/twitter/twemproxy/blob/master/src/nc_message.c#L27-L31 and redefine #define NC_IOV_MAX 1024 or #define NC_IOV_MAX 2048 Rerun...
for (1) see this: https://github.com/twitter/twemproxy/blob/master/notes/recommendation.md#liveness and this: https://github.com/twitter/twemproxy/blob/master/notes/recommendation.md#timeout. Let me know if you still have questions. for (2), I think jedis send a ping command on every new connection before...
try this patch: ``` diff diff --git a/src/nc_message.c b/src/nc_message.c index 654cdf9..84ef8e5 100644 --- a/src/nc_message.c +++ b/src/nc_message.c @@ -24,11 +24,7 @@ #include #include -#if (IOV_MAX > 128) -#define NC_IOV_MAX 128 -#else...
@neeleshkorade any updates on this?
@neeleshkorade sorry for the delay. Large buf size means less syscall from the writev() and read() because you are doing more in one syscall. However large buf size also means...
@zosxang mind signing the CLA before I merge this?
@charsyam I will take a look at this in next two days
@hrishimantri @sushantk I created a new branch -- twemproxy_heartbeat that contains @charsyam heartbeat patch. See: https://github.com/twitter/twemproxy/tree/twemproxy_heartbeat please use this branch to serve your needs. If no issues surface up after...
done - https://github.com/twitter/twemproxy/commit/049c34b3de8c23f5739f66aee7ad6924549bed18