GitHub PushEvent at 2014-05-22 20:03:11
Repository: redis
Actor: PKRoma
Payload: {"shas":[["4113473997358c2375c09f18715b4ef2e1fa7663","81516c0bc992c9cd30eeaa39d4784e98138d1c17@gmail.com","While ANET_ERR is -1, check syscall retval for -1 itself.","antirez",true],["f3d3c606f12ae090af4981f1262defde2b555b55","81516c0bc992c9cd30eeaa39d4784e98138d1c17@gmail.com","Accept multiple clients per iteration.\n\nWhen the listening sockets readable event is fired, we have the chance\nto accept multiple clients instead of accepting a single one. This makes\nRedis more responsive when there is a mass-connect event (for example\nafter the server startup), and in workloads where a connect-disconnect\npattern is used often, so that multiple clients are waiting to be\naccepted continuously.\n\nAs a side effect, this commit makes the LOADING, BUSY, and similar\nerrors much faster to deliver to the client, making Redis more\nresponsive when there is to return errors to inform the clients that the\nserver is blocked in an not interruptible operation.","antirez",true],["f4823497074eaa3b567e38313d6e85c9cf9ece9f","81516c0bc992c9cd30eeaa39d4784e98138d1c17@gmail.com","Process events with processEventsWhileBlocked() when blocked.\n\nWhen we are blocked and a few events a processed from time to time, it\nis smarter to call the event handler a few times in order to handle the\naccept, read, write, close cycle of a client in a single pass, otherwise\nthere is too much latency added for clients to receive a reply while the\nserver is busy in some way (for example during the DB loading).","antirez",true],["1a14eba2d50a494923531273fc1da63093689702","81516c0bc992c9cd30eeaa39d4784e98138d1c17@gmail.com","Test: fixed scripting.tcl test false positive.","antirez",true]],"size":4,"ref":"refs/heads/2.8","head":"1a14eba2d50a494923531273fc1da63093689702"}