[ 
https://issues.apache.org/jira/browse/KAFKA-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bill Bejeck updated KAFKA-5515:
-------------------------------
    Description: Currently the {{Segments}} class uses a date when calculating 
the segment id and uses {{SimpleDateFormat}} for formatting the segment id.  
However this is a high volume code path and creating a new {{SimpleDateFormat}} 
for each segment id is expensive.  We should look into removing the date from 
the segment id or at a minimum use a faster alternative to 
{{SimpleDateFormat}}.  We should also consider keeping a lookup of existing 
segments to avoid as many string operations as possible.  (was: Currently the 
{{Segments}} class uses a date when calculating the segment id and uses 
{{SimpleDateFormat}} for formatting the segment id.  However this is a high 
volume code path and creating a new {{SimpleDateFormat}} for each segment id is 
expensive.  We should look into removing the date from the segment id or at a 
minimum use a faster alternative to {{SimpleDateFormat}} )

> Consider removing date formatting from Segments class
> -----------------------------------------------------
>
>                 Key: KAFKA-5515
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5515
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: Bill Bejeck
>              Labels: performance
>
> Currently the {{Segments}} class uses a date when calculating the segment id 
> and uses {{SimpleDateFormat}} for formatting the segment id.  However this is 
> a high volume code path and creating a new {{SimpleDateFormat}} for each 
> segment id is expensive.  We should look into removing the date from the 
> segment id or at a minimum use a faster alternative to {{SimpleDateFormat}}.  
> We should also consider keeping a lookup of existing segments to avoid as 
> many string operations as possible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to