[
https://issues.apache.org/jira/browse/GEODE-9169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe updated GEODE-9169:
------------------------------
Comment: was deleted
(was: Seen in [integration-test-openjdk8
#140|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/integration-test-openjdk8/builds/140]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0431/test-results/integrationTest/1629827589/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0431/test-artifacts/1629827589/integrationtestfiles-openjdk8-1.15.0-build.0431.tgz].)
> Remove Context Switch Between Netty and Command Queue Thread
> ------------------------------------------------------------
>
> Key: GEODE-9169
> URL: https://issues.apache.org/jira/browse/GEODE-9169
> Project: Geode
> Issue Type: New Feature
> Components: redis
> Reporter: Wayne
> Assignee: Hale Bales
> Priority: Major
> Labels: blocks-1.15.0, performance, pull-request-available,
> redis
> Fix For: 1.15.0
>
>
> On the current develop branch, the Netty thread reads a message and then puts
> it on a queue for another thread to process. Performing the region update
> directly on the Netty thread significantly improved performance.
> The original behavior was there to support pub/sub use cases, where we need
> to push updates to the Netty channel, as well as following Netty best
> practices of not blocking the Netty thread. We need to see how we can make
> this same change on develop to avoid the context switch while still
> supporting pub/sub and not breaking other use cases.
> +Acceptance Criteria+
> The context switch between the Netty and command queue thread has been
> removed for all commands that are not pub/sub related.
> Geode benchmarks perform better after this change for all non-pubsub commands.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
