Difference between revisions of "Zaqar/Performance/PubSub/Redis"
< Zaqar | Performance
(initial content) |
m (→Configuration 1) |
||
| Line 15: | Line 15: | ||
* 1x1 redis (message store) | * 1x1 redis (message store) | ||
* 3x mongo replica set (pooling catalog) | * 3x mongo replica set (pooling catalog) | ||
| + | |||
| + | === Senario 1 === | ||
| + | |||
| + | In these tests, observers was held at 50 while the number of producer clients was steadily increased (X axis). This simulates a write-heavy workload. | ||
| + | |||
| + | ==== Mean Latency ==== | ||
| + | |||
| + | The Y-axis denotes mean latency in milliseconds. | ||
| + | |||
| + | [[File:Zaqar-juno-redis-pubsub-latency-mean-increasing-prod-50-obs.png]] | ||
Revision as of 22:10, 15 September 2014
Overview =
These tests examined the pub-sub performance of the Redis driver (Juno release).
Systems
TODO
Configuration 1
In these tests, various amounts of load was applied to the following configuration:
- 1x4 load balancer
- 1x20 web head (WSGI server)
- 1x1 redis (message store)
- 3x mongo replica set (pooling catalog)
Senario 1
In these tests, observers was held at 50 while the number of producer clients was steadily increased (X axis). This simulates a write-heavy workload.
Mean Latency
The Y-axis denotes mean latency in milliseconds.
