Now that a first version was cut, it seemed like a good time to start looking at how Cinched performs.
And I must say, things are looking good so far…
3 nodes in the Cinched cluster (each 4 vCPUs 4GB RAM)
1 node running the test harness (4 vCPUs, 4GB RAM).
My testing environment is extremely unreliable (VMs running in an overprovisioned cloud environment) so it’s been hard to get an extremely clear picture. Nevertheless, the numbers look promising.
The benchmark is run using my fork of basho_bench here against Cinched v0.0.3.
The test runs round robin operations cycling through the nodes in the cluster issuing requests for the various API endpoints.
API calls leverage HTTP keep-alives to amortize the cost of establishing the TCP handshake and TLS key exchange.
The document I’m encrypting is rather trivial:
Time: 60s Concurrency: 32
Time: 1 hour, Concurrency: 32
Time: 10 hours, Concurrency: 64