[
https://issues.apache.org/jira/browse/KAFKA-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-3534:
-----------------------------------
Affects Version/s: (was: 0.9.0.1)
0.10.0.0
0.10.0.1
0.10.1.0
0.10.1.1
0.10.2.0
> Deserialize on demand when default time extractor used
> ------------------------------------------------------
>
> Key: KAFKA-3534
> URL: https://issues.apache.org/jira/browse/KAFKA-3534
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Affects Versions: 0.10.0.0, 0.10.0.1, 0.10.1.0, 0.10.1.1, 0.10.2.0
> Reporter: Michael Coon
> Priority: Minor
> Labels: performance
>
> When records are added to the RecordQueue, they are deserialized at that time
> in order to extract the timestamp. But for some data flows where large
> messages are consumed (particularly compressed messages), this can result in
> large spikes in memory as all messages must be deserialized prior to
> processing (and getting out of memory). An optimization might be to only
> require deserialization at this stage if a non-default timestamp extractor is
> being used.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
