Skip to content

Instantly share code, notes, and snippets.

@ramanathanrv

ramanathanrv/gist:1364b92edc32b40c2449306880df197b

Last active March 31, 2019 16:22
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ramanathanrv/1364b92edc32b40c2449306880df197b to your computer and use it in GitHub Desktop.
Save ramanathanrv/1364b92edc32b40c2449306880df197b to your computer and use it in GitHub Desktop.
Download ZIP
Raw
gistfile1.md
Strategy Throughput (under similar test conditions) Trade off
#0 Cluster of nodes with Redis backend & 100% accurate 58K requests/sec (can be scaled out as required with additional hardware) Higher hardware cost & hardware footprint (linearly increasing)
#1 Use a single node to count & report 833K requests/sec Not HA. Can only scale up (not scale out)
#2 Use cluster of nodes but sync with Redis asynchronously 655K requests/sec Reporting is not realtime and hence solution is approximate rather than accurate
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment