Let’s Make Your CFO Happy; A Practical Guide for Kafka Cost Reduction with Elad Leev | Kafka Summit London 2022
•
0 likes•686 views
According to Gartner Forecasts, the worldwide end-user spending on public cloud services is forecast to grow by 23% in 2021, to a total of $332B. Kafka is no different in that matter. Organizations all over the world are using Kafka as their main stream-processing platform for collecting, processing, and analyzing data at scale. As organizations evolve and grow, data rates grow too, as does the consequent Kafka deployment cost. So what can we do? -- In this talk, we are going to address exactly this problem. We will understand what we are paying for when running a self-hosted Kafka deployment, where we can cut costs, how to develop an economic mindset, and what we can proactively do to reduce our cloud infrastructure cost.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Let’s Make Your CFO Happy; A Practical Guide for Kafka Cost Reduction with Elad Leev | Kafka Summit London 2022
Similar to Let’s Make Your CFO Happy; A Practical Guide for Kafka Cost Reduction with Elad Leev | Kafka Summit London 2022 (20)
More from HostedbyConfluent
More from HostedbyConfluent (20)
Recently uploaded
Recently uploaded (20)
Let’s Make Your CFO Happy; A Practical Guide for Kafka Cost Reduction with Elad Leev | Kafka Summit London 2022
- 1. Kafka Cost Reduction A Practical Guide for Let’s Make Your CFO Happy;
- 2. The Elephant In The Room What are we paying for? Running a self-hosted Kafka deployment Where and how can we cut costs? Tips, tricks, and KIPs Develop an economic mindset It’s part of our role
- 3. Elad Leev Data Engineer at Riskified @eladleev #DistributedSystems #DataStreams #Scalability #Kafka #ConfluentCommunityCatalyst
- 5. Riskified by the Numbers Global team, nearly 50% in engineering & analytics Countries across the globe Online volume (GMV) reviewed in 2021 750+ 180+ $89B 50+ Publicly held companies among our clients 98%+ Client retention* for the past 2 years *Annual dollar retention As of March 2022
- 7. According to Gartner Forecasts The worldwide end-user spending on public cloud services is forecast to grow by 20% in 2022 to a total of $397 billion. Source: Gartner (April 2021)
- 8. Data Never Sleeps According to Statista, the total amount of data consumed globally in 2021 was 79 Zettabytes.
- 9. of all Fortune 100 companies trust, and use Kafka. 80% More than
- 10. What are we paying for?
- 11. Kafka Deployment $ $ Kafka Cluster AWS Region Load Balancer Broker 1 AZ A AZ B AZ N Broker 3 Broker N
- 12. Kafka Cluster AWS Region Load Balancer Broker 1 AZ A AZ B AZ N Broker 3 Broker N Kafka Deployment $ $ EC2 Machines
- 13. Kafka Cluster AWS Region Load Balancer Broker 1 AZ A AZ B AZ N Broker 3 Broker N Kafka Deployment $ $ EC2 Machines EKS $
- 14. Kafka Cluster AWS Region Load Balancer Broker 1 AZ A AZ B AZ N Broker 3 Broker N Kafka Deployment $ $ EBS Drives $ $
- 15. Kafka Cluster AWS Region Load Balancer Broker 1 AZ A AZ B AZ N Broker 3 Broker N Kafka Deployment $ $ ZooKeepers $ $ $
- 16. Kafka Cluster AWS Region Load Balancer Broker 1 AZ A AZ B AZ N Broker 3 Broker N Kafka Deployment $ $ LB $ $ $ $
- 17. Kafka Cluster AWS Region Load Balancer Broker 1 AZ A AZ B AZ N Broker 3 Broker N Kafka Deployment $ $ $ $ $ $ Without consuming or producing a single byte
- 18. Kafka Cluster AWS Region Load Balancer Broker 1 AZ A AZ B AZ N Broker 3 Broker N Kafka Deployment $ $ $ $ $ $ $ Traffic
- 19. AWS Region AZ A AZ B AZ N Producer Consumer Producer Consumer Producer Kafka Deployment $ $ $ $ $ $ $ $ Traffic Traffic Kafka Cluster Load Balancer Broker 1 Broker 3 Broker N Traffic
- 20. AWS Region Management AZ A AZ B AZ N Metrics Logs Kafka Deployment $ $ $ $ $ $ $ $ Metrics Logs $ Producer Consumer Producer Consumer Producer Kafka Cluster Load Balancer Broker 1 Broker 3 Broker N
- 21. AWS Region Management AZ A AZ B AZ N Metrics Logs Kafka Deployment $ $ $ $ $ $ $ $ Kafka Connect $ $ Tools Connect Schema Registry Producer Consumer Producer Consumer Producer Kafka Cluster Load Balancer Broker 1 Broker 3 Broker N Schema Registry
- 22. AWS Region Management AZ A AZ B AZ N Metrics Logs Kafka Deployment $ $ $ $ $ $ $ $ Cruise Control $ $ Tools Connect Schema Registry Kafka UI $ UI Cruise Control Producer Consumer Producer Consumer Producer Kafka Cluster Load Balancer Broker 1 Broker 3 Broker N
- 23. AWS Region Management AZ A AZ B AZ N Metrics Logs Tools Connect Schema Registry UI Cruise Control Producer Consumer Producer Consumer Producer Kafka Cluster Load Balancer Broker 1 Broker 3 Broker N Kafka Deployment $ $ $ $ $ $ $ $ $ $ $ $ $ $ ● Multi Region ● Persist to S3 ● Mirror Maker ● Domain Separation
- 26. What can we do?
- 27. Instance type Compression Fetch from replica Cluster balance Tiered storage Client configuration fine tune 01 02 03 04 05 06
- 28. Are you using the right instance type? A quick Google search will suggest the R5, D2, C5 combined with GP2/3 or IO2 storage as the broad recommendation. C5 R5
- 29. Are you using the right instance type? Everything is a trade-off. Choose wisely based on your needs: Time-to-recover, Storage-to-dollar ratio, network throughput, EBS downfalls. Source: Liz Fong-Jones, Honeycomb.io
- 30. i3 and i3en for High-performance Kafka Deployments Despite the operational overhead of ephemeral drives.
- 31. i3en provides great storage-to-dollar ratio Suitable for I/O intensive deployments in which the limiting factor is storage capacity. Source: ScyllaDB
- 32. Are you using the right instance types? Is your cluster saturated? On what conditions? What is the limiting factor? Are EBS drives the right decision? Do the cluster needs changed over time?
- 33. Instance type Compression Fetch from replica Cluster balance Tiered storage Client configuration fine tune 01 02 03 04 05 06
- 34. Change compression type You can choose between GZIP, LZ4, Snappy, and since KIP-110 - ZSTD.
- 35. Zstandard Compression algorithm by Facebook It aims for a smaller and faster data compression. Meta
- 36. Real world examples Using Zstd, Shopify was able to get a 4.28x compression ratio compared to Snappy’s 2.5x. Average Message Size Bytes
- 37. After switching to Zstandard, our bandwidth usage decreased by 3x! This saves us tens of thousands of dollars per month in data transfer costs just from the processing pipeline alone. With these great results we immediately began deploying Zstandard to other systems in our architecture for further cost savings. “ Bandwidth usage “
- 38. KIP-390: Support Compression Level Zstd Level 1 produces 32.7% more messages per second than Zstd Level 3. Gzip Level 1 produces 56.4% more than Gzip Level 6. 29218 JSON files with an average size of 55.25kb
- 39. Instance type Compression Fetch from replica Cluster balance Tiered storage Client configuration fine tune 01 02 03 04 05 06
- 40. AWS Region AZ A AZ B AZ N Producer Consumer Producer Consumer Producer Kafka Cluster Load Balancer Broker 1 Broker 3 Broker N
- 41. AWS Region AZ A AZ B AZ N Producer Consumer Producer Consumer Producer Kafka Cluster Load Balancer Broker 1 Broker 3 Broker N
- 42. KIP-392: Fetch from closest replica Leverage locality in order to reduce expensive cross- AZ / cross-DC traffic costs.
- 43. KIP-392: Fetch from closest replica Rack awareness needs to be set. Support from the client is needed as well.
- 44. Instance type Compression Fetch from replica Cluster balance Tiered storage Client configuration fine tune 01 02 03 04 05 06
- 45. Cluster imbalance Might hurt cluster performance, lead to brokers skew, resource saturation, and as consequence - unnecessary capacity addition.
- 46. Cluster imbalance Overloaded brokers (more partitions, more segments) will suffer from higher MTTR. Source: plutora.com
- 47. AWS Region AZ A AZ B AZ N Producer Consumer Producer Consumer Producer Kafka Cluster Load Balancer Broker 1 Broker 3 Broker N Cluster imbalance Long startup time exposes you to a higher risk of data loss in case of cascading failures. ! !
- 48. Cluster imbalance Relatively easy-to-do task using- Cruise Control, CMAK, Kafka-Kit, and more. Cruise-control is the first of its kind to fully automate the dynamic workload rebalance and self-healing of a Kafka cluster. It provides great value to Kafka users by simplifying the operation of Kafka clusters.
- 49. Instance type Compression Fetch from replica Cluster balance Tiered storage Client configuration fine tune 01 02 03 04 05 06
- 50. Deep dive into the client configurations knobs can dramatically affect the way your cluster works Client Configurations
- 51. Clients Configurations Kafka just works out of the box. However to unlock its full potential - invest time in learning.
- 52. Clients Configurations For example, changing your clients batch.size and linger.ms configurations can reduce your cluster resource utilization.
- 53. Message Conversions Message conversion introduces a processing overhead. Upgrading clients can free up resources that were used unnecessarily for this task.
- 54. Instance type Compression Fetch from replica Cluster balance Tiered storage Client configuration fine tune 01 02 03 04 05 06
- 55. The Cluster Storage Kafka became the main entry point of all of the data in organizations, allowing clients to consume not only the recent events, but also older data based on the topic retention.
- 56. Upstream Clusters A common pattern is to split your cluster into smaller clusters based on business domains. Using this method you can set a higher retention period on the upstream cluster for data recovery in case of a failure. Upstream Cluster Raw Events Application A Application B Cluster Domain A Cluster Domain B DBZ Cluster Logging Cluster Downstream Cluster Application C Domain B Domain A S3 Amazon DynamoDB
- 57. Capacity addition Both cases require you to add disk capacity to support growth. High retention, justified by business needs, may lead to needless resource addition (memory and CPUs) to support storage capacity.
- 58. KIP-405: Kafka Tiered Storage Using Tiered Storage, Kafka clusters are configured with two tiers of storage: local and remote. The new remote tier uses external object storage layers such as AWS S3 or HDFS.
- 59. Kafka Tiered Storage Storage cost saving ~$0.08 per GB on gp3 Vs. ~$0.023 on S3 01 Accurate capacity planning Mostly based on computing power, and not storage 02 Scaling storage Independently from memory and CPUs 03 Remove unnecessary capacity Remove capacity that has been added to support long-term retention 04 Faster broker startup Loading local (and fewer) segments on broker startup 05 Tiered Storage is already available on Confluent Platform 6.0.0, and will be added to the Kafka 3.2 release.
- 60. The TL;DL (Too Long ; Didn't Listen)
- 61. Cost Reduction Areas Machine Network Storage Instance Type Compression Fetch from Close Replica Cluster Balance Consumer Tune Producer Tune Compression Levels Tiered Storage