Zakelly opened a new pull request, #26005:
URL: https://github.com/apache/flink/pull/26005

   ## What is the purpose of the change
   
   Currently, if user enables the async state processing, and use one state 
backends supporting async state access (e.g. ForSt State Backend), but invokes 
synchronous methods (e.g. `get()`, `add()`), there is performance issue for 
state access. The default implementation of synchronous methods for the case 
above is submitting a async state access and wait. This PR applies an 
optimization that bypass all the async executions and just access the state in 
synchronous way.
   
   
   ## Brief change log
   
    - Provide `sync` flag in `StateRequest` and if it is ready to execute, fire 
it synchronously.
   
   ## Verifying this change
   
   This change is already covered by existing tests.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): yes
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to