flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yu Li (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-11986) Add micro benchmark for state operations
Date Wed, 01 May 2019 06:25:00 GMT

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

Yu Li resolved FLINK-11986.
---------------------------
       Resolution: Implemented
    Fix Version/s: 1.9.0

PR already merged and integrated into our Jenkins and [SpeedCenter|http://codespeed.dak8s.net:8000/timeline/#/?exe=3&ben=grid&env=2&revs=200&equid=off&quarts=on&extr=on],
closing issue. Thanks [~pnowojski] for review and merge the PR, and thanks [~srichter] for
review.

> Add micro benchmark for state operations
> ----------------------------------------
>
>                 Key: FLINK-11986
>                 URL: https://issues.apache.org/jira/browse/FLINK-11986
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / State Backends, Tests
>            Reporter: Yu Li
>            Assignee: Yu Li
>            Priority: Major
>             Fix For: 1.9.0
>
>
> Currently in the [flink-benchmark|https://github.com/dataArtisans/flink-benchmarks] project
we already have a JMH case for the whole backend, but none for finer grained state operations,
and here we propose adding JMH cases for them, including (but not limited to):
>  * ValueState
>  ** testPut
>  ** testGet
>  * ListState
>  ** testUpdate
>  ** testGet
>  ** testAddAll
>  * MapState
>  ** testPut
>  ** testGet
>  ** testContains
>  ** testKeys
>  ** testValues
>  ** testEntries
>  ** testIterator
>  ** testRemove
>  ** testPutAll
> And we will create benchmark for {{HeapKeyedStateBackend}} and {{RocksDBKeyedStateBackend}}
separately.
> We believe these micro benchmarks could help locate where the regression comes from in
case any observed from the backend benchmark, and we could also use these benchmarks to assure
no performance downgrade when modifying relative codes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message