This is an old benchmark result that test Redis and Aerospike, both are in-memory database, I did this about December last year, that I used to test Redis agains Aerospike for cases of storing random session per request:
Redis (redigo)
Transactions: 52343 hits
Availability: 100.00 %
Elapsed time: 9.16 secs
Data transferred: 17.02 MB
Response time: 0.04 secs
Transaction rate: 5714.30 trans/sec (1654 worst >1M uQ sess)
Throughput: 1.86 MB/sec
Concurrency: 252.55
Successful transactions: 52343
Failed transactions: 0
Longest transaction: 1.13
Shortest transaction: 0.00
Aerospike (aerospike-client-go)
Transactions: 80806 hits
Availability: 100.00 %
Elapsed time: 9.71 secs
Data transferred: 26.28 MB
Response time: 0.03 secs
Transaction rate: 8321.94 trans/sec (8999 best, 7769 worst)
Throughput: 2.71 MB/sec
Concurrency: 251.91
Successful transactions: 80806
Failed transactions: 0
Longest transaction: 1.17
Shortest transaction: 0.00
Redis (go-redis)
Transactions: 91187 hits
Availability: 100.00 %
Elapsed time: 9.95 secs
Data transferred: 29.65 MB
Response time: 0.03 secs
Transaction rate: 9164.52 trans/sec (3536 worst >1M uQ sess)
Throughput: 2.98 MB/sec
Concurrency: 252.70
Successful transactions: 91187
Failed transactions: 0
Longest transaction: 0.20
Shortest transaction: 0.00
The bad part about Redis (that uses SkipList), more data we store, it slows down faster, in this case 1 million sessions stored slows Redis down by more than 60%, while Aerospike only slowed down by 10%).
