1. 08 May, 2014 2 commits
    • antirez's avatar
      DEBUG embstr-classes added. · 7c6b8ec6
      antirez authored
      7c6b8ec6
    • antirez's avatar
      Use a free list for EMBSTR objects creation / release. · 19f735ce
      antirez authored
      To my surprise, mantaining a small poll of objects provides a very big
      speedup even when the jemalloc allocator is used, which is supposed to
      have arenas doing mostly the same work.
      
      Probably this is a combination of different factors:
      
      1) No need to manage zmalloc total memory used.
      2) No locking of any kind because we can assume single thread, so
         maintaining the free list may be cheaper for us compared to
         jemalloc.
      3) More locality because of a different cache/reuse pattern?
      19f735ce
  2. 07 May, 2014 12 commits
  3. 02 May, 2014 5 commits
  4. 30 Apr, 2014 3 commits
  5. 29 Apr, 2014 8 commits
    • antirez's avatar
      CLUSTER SET-CONFIG-EPOCH implemented. · 11d9ecb7
      antirez authored
      Initially Redis Cluster accepted that after cluster creation all the
      nodes were at configEpoch 0, evolving from zero as failovers happen.
      
      However later the semantic was made more strict in order to make sure a
      cluster has always all the master nodes with a different configEpoch,
      which is more robust in some corner case (especially resulting from
      errors by the system administrator).
      
      To assign different configEpochs to different nodes at startup was a
      task performed naturally by the config conflicts resolution algorithm
      (see the Cluster specification). However this works well only for small
      clusters or when there are actually just a few collisions, since it is
      designed for exceptional cases.
      
      When a large cluster is created hundred of nodes can be at epoch 0, so
      the conflict resolution code is slow to provide an unique config to each
      node. For this reason this new command was introduced. It can be called
      only when a node is totally fresh: no other nodes known, and configEpoch
      set to zero, so it is safe even against misuses.
      
      redis-trib will use the new command in order to start the cluster
      already setting an incremental unique config to every node.
      11d9ecb7
    • antirez's avatar
      Cluster test: slots allocation. · 7b5ce1ff
      antirez authored
      7b5ce1ff
    • antirez's avatar
      Cluster test: use 20 instances. · 4a3db255
      antirez authored
      This makes tests a bit slower, but it is better to test things at a
      decent scale instead of using just a few nodes, and for a few tests we
      actually need so many nodes.
      4a3db255
    • antirez's avatar
      e8631a69
    • antirez's avatar
      Cluster test: config epoch conflict resolution. · 9e422f74
      antirez authored
      9e422f74
    • antirez's avatar
      Cluster test: auto-discovery to form full mesh. · 2c556223
      antirez authored
      2c556223
    • antirez's avatar
      2555b2f4
    • antirez's avatar
      e1b12981
  6. 28 Apr, 2014 4 commits
  7. 24 Apr, 2014 6 commits
    • antirez's avatar
      Test: fixed scripting.tcl test false positive. · 93e7a130
      antirez authored
      93e7a130
    • antirez's avatar
      Process events with processEventsWhileBlocked() when blocked. · e29d3307
      antirez authored
      When we are blocked and a few events a processed from time to time, it
      is smarter to call the event handler a few times in order to handle the
      accept, read, write, close cycle of a client in a single pass, otherwise
      there is too much latency added for clients to receive a reply while the
      server is busy in some way (for example during the DB loading).
      e29d3307
    • antirez's avatar
      Accept multiple clients per iteration. · 3a3458ee
      antirez authored
      When the listening sockets readable event is fired, we have the chance
      to accept multiple clients instead of accepting a single one. This makes
      Redis more responsive when there is a mass-connect event (for example
      after the server startup), and in workloads where a connect-disconnect
      pattern is used often, so that multiple clients are waiting to be
      accepted continuously.
      
      As a side effect, this commit makes the LOADING, BUSY, and similar
      errors much faster to deliver to the client, making Redis more
      responsive when there is to return errors to inform the clients that the
      server is blocked in an not interruptible operation.
      3a3458ee
    • antirez's avatar
      AE_ERR -> ANET_ERR in acceptUnixHandler(). · cac4bae1
      antirez authored
      No actual changes since the value is the same.
      cac4bae1
    • antirez's avatar
      Redis Cluster test framework skeleton. · c3f85c01
      antirez authored
      c3f85c01
    • antirez's avatar
      7d9b45b4