antirez
eb3d93fd27
add -f flag to cp when installing, otherwise stopping the server is
...
needed when installing a new Redis version. Thanks to Scott Kevill.
Fixes issue #335 .
2012-02-14 16:15:24 +01:00
antirez
120a36f22b
add -f flag to cp when installing, otherwise stopping the server is
...
needed when installing a new Redis version. Thanks to Scott Kevill.
Fixes issue #335 .
2012-02-14 16:15:24 +01:00
antirez
9a68f79cd5
endian.c/h -> endianconv.c/h to avoid issues with broken libraries search paths.
2012-02-14 16:11:46 +01:00
antirez
7a3e372025
endian.c/h -> endianconv.c/h to avoid issues with broken libraries search paths.
2012-02-14 16:11:46 +01:00
antirez
40bf784fbf
Merge remote-tracking branch 'origin/unstable' into unstable
2012-02-14 16:02:04 +01:00
antirez
18aa2b87b6
Merge remote-tracking branch 'origin/unstable' into unstable
2012-02-14 16:02:04 +01:00
antirez
55e02e58fa
intset.c endianess fixes.
2012-02-14 15:35:50 +01:00
antirez
6136a16bd1
intset.c endianess fixes.
2012-02-14 15:35:50 +01:00
lsbardel
35a943766b
added lua struct c extension
2012-02-13 21:05:21 +00:00
lsbardel
2f75bbab02
added lua struct c extension
2012-02-13 21:05:21 +00:00
antirez
f03979dbaf
ziplist.c endianess fixes, chapter 5.
2012-02-09 17:09:01 +01:00
antirez
66d1b021ec
ziplist.c endianess fixes, chapter 5.
2012-02-09 17:09:01 +01:00
antirez
b87552bbb1
ziplist.c endianess fixes, chapter 4.
2012-02-09 16:36:25 +01:00
antirez
cab1105c6e
ziplist.c endianess fixes, chapter 4.
2012-02-09 16:36:25 +01:00
antirez
2b6f42d9de
ziplist.c endianess fixes, chapter 3.
2012-02-09 16:28:35 +01:00
antirez
3fa19b7dfc
ziplist.c endianess fixes, chapter 3.
2012-02-09 16:28:35 +01:00
antirez
ab401f90d8
more ziplist.c endianess fixes
2012-02-08 23:20:39 +01:00
antirez
8e0ef249a2
more ziplist.c endianess fixes
2012-02-08 23:20:39 +01:00
antirez
b10e6ebb86
ziplist.c fixes for bigendian
2012-02-08 22:59:35 +01:00
antirez
5653847714
ziplist.c fixes for bigendian
2012-02-08 22:59:35 +01:00
antirez
3fcae1cc78
A few small BSD related fixes.
2012-02-08 22:24:59 +01:00
antirez
ac834d237a
A few small BSD related fixes.
2012-02-08 22:24:59 +01:00
antirez
bd66a75484
debugging messages removed from freeMemoryIfNeeded()
2012-02-08 00:10:20 +01:00
antirez
b129c6df45
debugging messages removed from freeMemoryIfNeeded()
2012-02-08 00:10:20 +01:00
antirez
97f45bad9b
Fixes to c->reply_bytes computation, and debug messages to closely study the behavior of memory pressure + slaves + maxmemory + blocked slaves.
2012-02-07 17:41:31 +01:00
antirez
609baba8a2
Fixes to c->reply_bytes computation, and debug messages to closely study the behavior of memory pressure + slaves + maxmemory + blocked slaves.
2012-02-07 17:41:31 +01:00
antirez
f57707f408
Precision of getClientOutputBufferMemoryUsage() greatily improved, see issue #327 for more information.
2012-02-07 13:05:36 +01:00
antirez
442246dde2
Precision of getClientOutputBufferMemoryUsage() greatily improved, see issue #327 for more information.
2012-02-07 13:05:36 +01:00
antirez
0de0faf4a0
freeMemoryIfNeeded() minor refactoring
2012-02-06 16:56:42 +01:00
antirez
8b7c3455b9
freeMemoryIfNeeded() minor refactoring
2012-02-06 16:56:42 +01:00
antirez
31ae67e8ce
Also remove size of AOF buffers from used memory when doing the math for freeMemoryIfNeeded()
2012-02-06 16:35:43 +01:00
antirez
c1ef6ffe8a
Also remove size of AOF buffers from used memory when doing the math for freeMemoryIfNeeded()
2012-02-06 16:35:43 +01:00
antirez
06909a2241
Redis Manifesto moved from src to root dir
2012-02-05 09:37:08 +01:00
antirez
7441fcdd56
Redis Manifesto moved from src to root dir
2012-02-05 09:37:08 +01:00
antirez
ee273aa92c
This fixes issue #327 , is a very complex fix (unfortunately), details:
...
1) sendReplyToClient() now no longer stops transferring data to a single
client in the case we are out of memory (maxmemory-wise).
2) in processCommand() the idea of we being out of memory is no longer
the naive zmalloc_used_memory() > server.maxmemory. To say if we can
accept or not write queries is up to the return value of
freeMemoryIfNeeded(), that has full control about that.
3) freeMemoryIfNeeded() now does its math without considering output
buffers size. But at the same time it can't let the output buffers to
put us too much outside the max memory limit, so at the same time it
makes sure there is enough effort into delivering the output buffers to
the slaves, calling the write handler directly.
This three changes are the result of many tests, I found (partially
empirically) that is the best way to address the problem, but maybe
we'll find better solutions in the future.
2012-02-04 14:05:54 +01:00
antirez
f6b32c14f4
This fixes issue #327 , is a very complex fix (unfortunately), details:
...
1) sendReplyToClient() now no longer stops transferring data to a single
client in the case we are out of memory (maxmemory-wise).
2) in processCommand() the idea of we being out of memory is no longer
the naive zmalloc_used_memory() > server.maxmemory. To say if we can
accept or not write queries is up to the return value of
freeMemoryIfNeeded(), that has full control about that.
3) freeMemoryIfNeeded() now does its math without considering output
buffers size. But at the same time it can't let the output buffers to
put us too much outside the max memory limit, so at the same time it
makes sure there is enough effort into delivering the output buffers to
the slaves, calling the write handler directly.
This three changes are the result of many tests, I found (partially
empirically) that is the best way to address the problem, but maybe
we'll find better solutions in the future.
2012-02-04 14:05:54 +01:00
antirez
ea71e06988
Use less memory when emitting the protocol, by using more shared objects for commonly emitted parts of the protocol.
2012-02-04 08:58:37 +01:00
antirez
355f859134
Use less memory when emitting the protocol, by using more shared objects for commonly emitted parts of the protocol.
2012-02-04 08:58:37 +01:00
antirez
67c4a45d53
Now Lua scripts dispatch Redis commands properly calling the call() function. In order to make this possible call() was improved with a new flags argument that controls how the Redis command is executed.
2012-02-02 16:30:52 +01:00
antirez
ce8b772be7
Now Lua scripts dispatch Redis commands properly calling the call() function. In order to make this possible call() was improved with a new flags argument that controls how the Redis command is executed.
2012-02-02 16:30:52 +01:00
antirez
90754849a9
Set a 3.5 GB maxmemory limit with noeviction policy if a 32 bit instance without user-provided memory limits is detected.
2012-02-02 10:26:20 +01:00
antirez
d876678b5e
Set a 3.5 GB maxmemory limit with noeviction policy if a 32 bit instance without user-provided memory limits is detected.
2012-02-02 10:26:20 +01:00
antirez
0671914638
Added a server.arch_bits field instead of computing it at runtime for INFO.
2012-02-02 10:23:31 +01:00
antirez
75eaac5c74
Added a server.arch_bits field instead of computing it at runtime for INFO.
2012-02-02 10:23:31 +01:00
antirez
c814e1baca
Only incremnet stats for key miss/hit when the key is semantically accessed in read-only.
2012-02-01 21:51:20 +01:00
antirez
b80b1c5914
Only incremnet stats for key miss/hit when the key is semantically accessed in read-only.
2012-02-01 21:51:20 +01:00
antirez
d26bae3ce9
Make SORT BY <constant> STORE ... to always produce the same output by force sorting, so that we have deterministic replication of this command.
2012-02-01 17:05:45 +01:00
antirez
de79a2ee12
Make SORT BY <constant> STORE ... to always produce the same output by force sorting, so that we have deterministic replication of this command.
2012-02-01 17:05:45 +01:00
antirez
4a6e6ac8e6
SORT is now more deterministic: does not accept to compare by score items that have scores not representing a valid double. Also items with the same score are compared lexycographically. At the same time the scripting side introduced the ability to sort the output of SORT when sort uses the BY <constant> optimization, resulting in no specific ordering. Since in this case the user may use GET, and the result of GET can be null, converted into false as Lua data type, this commit also introduces the ability to sort Lua tables containining false, only if the first (faster) attempt at using just table.sort with a single argument fails.
2012-02-01 15:22:28 +01:00
antirez
2c861050c1
SORT is now more deterministic: does not accept to compare by score items that have scores not representing a valid double. Also items with the same score are compared lexycographically. At the same time the scripting side introduced the ability to sort the output of SORT when sort uses the BY <constant> optimization, resulting in no specific ordering. Since in this case the user may use GET, and the result of GET can be null, converted into false as Lua data type, this commit also introduces the ability to sort Lua tables containining false, only if the first (faster) attempt at using just table.sort with a single argument fails.
2012-02-01 15:22:28 +01:00
