You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Roman Grebennikov (Jira)" <ji...@apache.org> on 2019/12/11 09:47:00 UTC
[jira] [Updated] (FLINK-15171) Performance regression in
serialisation benchmarks
[ https://issues.apache.org/jira/browse/FLINK-15171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Grebennikov updated FLINK-15171:
--------------------------------------
Attachment: dec11.svg
dec05.svg
> Performance regression in serialisation benchmarks
> --------------------------------------------------
>
> Key: FLINK-15171
> URL: https://issues.apache.org/jira/browse/FLINK-15171
> Project: Flink
> Issue Type: Bug
> Components: API / Type Serialization System, Benchmarks
> Affects Versions: 1.10.0
> Reporter: Piotr Nowojski
> Assignee: Roman Khachatryan
> Priority: Blocker
> Fix For: 1.10.0
>
> Attachments: dec05.svg, dec11.svg
>
>
> There is quite significant performance regression in serialisation benchmarks in the commit range 2ecf7ca..9320f34 (which includes FLINK-14346).
> http://codespeed.dak8s.net:8000/timeline/?ben=serializerTuple&env=2
> http://codespeed.dak8s.net:8000/timeline/?ben=serializerRow&env=2
> http://codespeed.dak8s.net:8000/timeline/?ben=serializerPojo&env=2
> it coincides with the performance improvement for heavy strings
> http://codespeed.dak8s.net:8000/timeline/?ben=serializerHeavyString&env=2
> it might be caused by some accidental change in the benchmarking code (changing parallelism in one benchmarks is carried on to the next one?) or in the code itself.
> CC [~rgrebennikov] [~AHeise]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)