[
https://issues.apache.org/jira/browse/KAFKA-6761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468244#comment-16468244
]
ASF GitHub Bot commented on KAFKA-6761:
---------------------------------------
bbejeck opened a new pull request #4983: KAFKA-6761 [WIP]- reduce streams
footprint part II
URL: https://github.com/apache/kafka/pull/4983
This version is a WIP and intentionally leaves out some additional required
changes to keep the reviewing effort more manageable. This version of the
process includes
1. Cleaning up the graph objects to reduce the number of parameters and make
the naming conventions more clear.
2. Intercepting all calls to the `InternalToplogyBuilder` and capturing all
details required for possible optimizations and building the final topology.
This PR does not include writing out the current physical plan, so no tests
included. The next PR will include additional changes to building the graph
and writing the topology out without optimizations, using the current streams
tests.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Reduce Kafka Streams Footprint
> ------------------------------
>
> Key: KAFKA-6761
> URL: https://issues.apache.org/jira/browse/KAFKA-6761
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Bill Bejeck
> Assignee: Bill Bejeck
> Priority: Major
> Fix For: 2.0.0
>
>
> The persistent storage footprint of a Kafka Streams application contains the
> following aspects:
> # The internal topics created on the Kafka cluster side.
> # The materialized state stores on the Kafka Streams application instances
> side.
> There have been some questions about reducing these footprints, especially
> since many of them are not necessary. For example, there are redundant
> internal topics, as well as unnecessary state stores that takes up space but
> also affect performance. When people are pushing Streams to production with
> high traffic, this issue would be more common and severe. Reducing the
> footprint of Streams have clear benefits for reducing resource utilization of
> Kafka Streams applications, and also not creating pressure on broker's
> capacities.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
