- 27 5月, 2009 3 次提交
- 26 5月, 2009 6 次提交
-
-
由 antirez 提交于
ignore gcc warning about write() return code not checked. It is esplicitily this way since the "max number of clients reached" is a best-effort error
-
由 antirez 提交于
-
由 antirez 提交于
RubyRedis: set TCP_NODELAY TCP socket option to to disable the neagle algorithm. Makes a huge difference under some OS, notably Linux
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
- 24 5月, 2009 2 次提交
- 23 5月, 2009 7 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
replication slave timeout when receiving the initial bulk data set to 3600 seconds, now that replication is non-blocking the server must save the db before to start the async replication and this can take a lot of time with huge datasets
-
由 antirez 提交于
-
由 antirez 提交于
critical bug about glueoutputbuffers=yes fixed. Under load and with pipelining and clients disconnecting on the middle of the chat with the server, Redis could block. Now it's ok
-
- 22 5月, 2009 6 次提交
- 21 5月, 2009 3 次提交
- 20 5月, 2009 10 次提交
- 19 5月, 2009 1 次提交
-
-
由 antirez 提交于
psort.c/h added. This is a partial qsort implementation that Redis will use when SORT+LIMIT is requested
-
- 18 5月, 2009 2 次提交
-
-
由 Aman Gupta 提交于
-
由 Aman Gupta 提交于
-