Giter VIP home page Giter VIP logo

Comments (3)

heyitsanthony avatar heyitsanthony commented on July 30, 2024 1

There have been performance improvements since then on both etcd and zetcd, but another round of benchmarks would be needed to quantify the impact. If performance has gotten worse, there's a regression.

from zetcd.

IgorPerikov avatar IgorPerikov commented on July 30, 2024

Thanks, Anthony. Any plans about this benchmarks? If you do should I convert this issue to tracking issue about them?

from zetcd.

jpiper avatar jpiper commented on July 30, 2024

I just ran zkboom on a deployment backed by a 5-node etcd v3.3.2 cluster, attempting to replicate the table shown here:https://coreos.com/blog/introducing-zetcd. I compiled the latest zetcd HEAD and vendored in etcd v3.3.2 and gRPC v1.7.5 as well.

For a single zetcd replica and small numbers of concurrent clients, things are much faster than the blog post. However, the write latencies are higher once you hit 50 concurrent clients. This may be expected - my 5-node cluster will have a higher write latency than a 3 or 1 node cluster (I don't know what was used in the blog post) Likewise, my etcd peer and client connections are secured with TLS which could incur a performance hit.

If I set an overall request limit to 500/s, I get an average write latency of 30ms, so it looks like running without a limit it just hammering zetcd, and it can't really handle more than 500 writes a second on my setup.

$ zkboom --key-size 128 --val-size 128 --total=10000 --rate=2500 --conns=$CONNS  --endpoints zetcd:2181 create
+-------+---------+--------------------------+
| conns |  HEAD   |  v0.0.1 (from blog post) |
+-------+---------+--------------------------+
|     1 | 3.2ms   | 12.5ms                   |
|     5 | 7.5ms   | 31.25ms                  |
|    10 | 13ms    | 37.5ms                   |
|    25 | 44ms    | 44ms                     |
|    50 | 100ms   | 44ms                     |
+-------+---------+--------------------------+

To put this in comparison with a real 5-node zookeeper deployment, I can run zkboom with 50 connections and get 2.8k op/s - 5x higher throughput than zetcd and with much lower latency. Unless I've done something terribly wrong, this only seems like zetcd is useful if you're expecting less than 500 writes a second.

Summary:
  Total:	3.9995 secs.
  Slowest:	0.0123 secs.
  Fastest:	0.0003 secs.
  Average:	0.0007 secs.
  Stddev:	0.0005 secs.
  Requests/sec:	2500.2825

from zetcd.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.