To increase consumerthroughput, one effective strategy is toincrease the amount of datafetched in each poll by raisingfetch.max.bytesormax.partition.fetch.bytes. This allows each poll to retrieve more records per request, improving processing efficiency.
FromKafka Consumer Config Docs:
"Increasing fetch size allows consumers to retrieve larger batches of messages, improving throughput and reducing request overhead."
* Removing consumers (A) may reduce parallelism.
* Manual commit (C) adds complexity, not throughput.
* Decreasing session timeout (D) risks unnecessary rebalances.
Reference:Kafka Consumer Configuration > fetch.max.bytes

min.insync.replicas does not impact producers when acks=1 (only when acks=all)

With SSL, messages will need to be encrypted and decrypted, by being first loaded into the JVM, so you lose the zero copy optimization. See more information herehttps://twitter.com/ijuma/status/1161303431501324293?s=09

See https://stackoverflow.com/a/37748336/3019499

A hopping window is defined by two propertiesthe window's size and its advance interval (aka "hop"), e.g., a hopping window with a size 5 minutes and an advance interval of 1 minute.