Re:Show HN: Kubestone – Benchmarking Operator for Kubernetes
by jacques_chester on Sunday November 17, 2019 @11:11AM
(#21558510)
How do you disentangle the performance effects of load generation from the target system? It looks at first glance to all be colocated in the same cluster.
Re:Show HN: Kubestone – Benchmarking Operator for Kubernetes
by ottovonbivouac on Sunday November 17, 2019 @04:05PM
(#21560046)
You can use taints, tolerations, affinity and anti-affinity of k8s to schedule the load-generator to a different node than the one contains the service under test.
The load-gen and the service does not need to be co-located in case of REST (drill) and PostgreSQL (pgbench) based load testing.
In case of pure network benchmarking (with iperf & qperf) currently only the same cluster is supported.
Re:Show HN: Kubestone – Benchmarking Operator for Kubernetes
by noodlesUK on Sunday November 17, 2019 @08:55AM
(#21557913)
Just so as you know, there’s something funky going on with your domain. I’m on mobile right now, so I’m not sure what, but I can’t resolve it on my home network, I expect it’s something perhaps to do with dnssec.
Re:Show HN: Kubestone – Benchmarking Operator for Kubernetes
by ottovonbivouac on Sunday November 17, 2019 @04:08PM
(#21560059)
The idea came when we tried to optimize Cluster filesystem (CEPH via Rook) for K8S. During this exercise we needed to test both PV&PVC performance, as well as TCP latency and bandwidths.
Target audience would be Kubernetes and OpenShift administrators who would like to measure and tune their installations. It is convenient for them as one CR can be used to describe the performance measurement.
The load-gen and the service does not need to be co-located in case of REST (drill) and PostgreSQL (pgbench) based load testing.
In case of pure network benchmarking (with iperf & qperf) currently only the same cluster is supported.
Any plan to include other load generators, such as JMeter [1] or Locust [2]?
1: https://jmeter.apache.org 2: https://locust.io
What we have as of today is Drill support, which is a HTTP load tester with Ansible like syntax:
- Drill GitHub page: https://github.com/fcsonline/drill
- kubestone doc for drill: https://kubestone.io/en/latest/benchmarks/drill/
https://github.com/xridge/kubestone/issues/159
https://github.com/xridge/kubestone/issues/160
Thanks!
This looks no different than STRIPE.COM (which, of course, is also not signed).
https://dnssec-analyzer.verisignlabs.com/stripe.com
Target audience would be Kubernetes and OpenShift administrators who would like to measure and tune their installations. It is convenient for them as one CR can be used to describe the performance measurement.