jamiealquiza/sangrenel

Apache Kafka load testing "...basically a cloth bag filled with small jagged pieces of scrap iron"

sangrenel's Issues

add overhead % in output

Track % of time spent not actually sending messages, rather, preparing them (e.g. batch assembly)

code.google.com/p/snappy-go/snappy moved to github.com/google/snappy

github.com/jamiealquiza/sangrenel/vendor/github.com/Shopify/sarama/snappy.go: "code.google.com/p/snappy-go/snappy" moved to "github.com/google/snappy"

$ go get github.com/jamiealquiza/sangrenel
package github.com/jamiealquiza/sangrenel
imports code.google.com/p/snappy-go/snappy: unable to detect version control system for code.google.com/ path

message batching is broken

Add auto-tuning mode for autonomously discovering Kafka performance

Sangrenel has great input controls such as worker concurrency, message sizes and rate limits - so that Kafka cluster can be observed within a controlled environment. Would be nice if performance thresholds could be pre-defined, such as a desired 90th percentile and worst case latency treshold, and Sangrenel automatically adjusts workers & message rates to tell you what a spec'd cluster should be suitable to handle in terms of throughput. For example, "I just built a 6 node Dell R420 cluster, how much throughput can this handle while maintaining a sub 10ms latency?" - The user should enter '10ms', a run duration, fire up Sangrenel and walk away for a jam cookie while the service does the work for them.

add required acks config

Invalid API version options

Hi,
The API version returns the wrong list of options, it make me confused. You can see bellow pic, even with the correct 2.2.0.0 option, it still invalid.

Needs an RPS metric

Report request rate from the Sarama client.

Add clustering

Single c3.8xlarge caps out @ ~3Gb/s. output. Need to build Sangrenel clustering with centralized controls and a working distributed rate limiter.

Update the vendored Sarama client

It's time.

add compression controls

arf

I mean, of course.

Better latency calcs

Will probably refine / incorporate tachymeter

add required ack controls

add message/batch encoding timer

Add AsyncProducer option?

From what I can tell, Sangrenel uses sync producers (right?). If so, it would be nice to be able to play around with an async producer as well to observe the batch sending from the producer side and observe how well the brokers handle different incoming batch sizes.

Invalid API versions after #59 merged

Hey @jamiealquiza. #59 fixes #58 but the invalid API versions appear yet again in the code.

Better metrics output

Replace the janky graphite option.

add error rate

new release version

Could you make a new release version in github?

The current latest actually has quite a few different features then master. Having it be the latest release was a little confusing when I tried sangrenel out.

Thanks!

protocol version control

make the tachymeter resize safe

Causes a crash.

allow a fixed range for the histogram

Predict / allocate a sensible []latency capacity

Reduce rapid slice growth.

add batching controls

Provide options for authentication

I currently see no way to use this tool with Kafka cluster that requires authentication. (other than SSL).

In my case we are using SASL_PLAINTEXT and SCRAM-SHA-256, which would imply providing username/password when attempting to authentication. I currently see no option to supply those.

It either needs to be implemented or it needs to be documented (if already implemented).

Add additional info outputs

Sangrenel dumps periodic output to console, which is easily parsed for input elsewhere. Would be better to have things like:

• native output into Graphite so that Sangrenel data can be overlaid with external but relevant data (e.g. Kafka node metrics).
• an option to run for a fixed period and dump a report in addition to the periodic info output

configurable Sarama API version

Needs better clarity/controls on the underlying Sarama client

As noted in my blog post, benchmarking is complicated; this tool effectively couples (beyond just a Kafka cluster) the Sarama client as a piece of the performance testing. Underlying factors such as batching, connection counts and other controls have significant effects. These effects in relation to Sangrenel need to be clarified and controls need to be exposed where needed.

add tachymeter html graph writing options

rate slowly creeps up with rate-limiter applied

support a message template file

Allow a template file pre-loaded with sample message to be used. Not only will it more closely resemble user-specific data, but compression performance will be more realistically represented (compressing the Sangrenel generated random data doesn't result in high ratios).

kafka: client has run out of available brokers to talk to (Is your cluster reachable?)

When I run sangrenel in Centos , I face bellow error;

# sangrenel 
Starting 1 client workers, 5 writers per worker
Message size 300 bytes, 500 message limit per batch
API Version: automatic, Compression: none, RequiredAcks: local
2020/02/19 14:05:12 kafka: client has run out of available brokers to talk to (Is your cluster reachable?)

any thoughts?

Add message template support

Completely random messages have limited value. Sangrenel needs a template system that allows users to model messages that more accurately reflect real world data.

Add notice if sampling occurred

breakage

panic: strings: negative Repeat count

goroutine 1 [running]:
strings.Repeat(0x710b59, 0x1, 0x8000000000000000, 0x0, 0xc42373a000)
        /usr/local/go/src/strings/strings.go:432 +0x258
github.com/jamiealquiza/tachymeter.(*Histogram).String(0xc420aa5ea0, 0x32, 0xc42270df28, 0x5)
        /home/jamiealquiza/go/src/github.com/jamiealquiza/tachymeter/tachymeter.go:271 +0x2a6
main.main()
        /home/jamiealquiza/go/src/github.com/jamiealquiza/sangrenel/sangrenel.go:161 +0xd72

up default batch size