[
https://issues.apache.org/jira/browse/IGNITE-25086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-25086:
--------------------------------------
Description: Currently, all sql-related requests are processed on the
thread assigned to client connection. Given that preparation sometimes may take
a while, and at the end operation anyway will be rescheduled to another thread
pool, we can improve scalability by rescheduling request processing immediately
to a thread which is allowed to execute storage operation. (was: Currently,
all sql-related requests are processed on the same thread. Given that
preparation sometimes may take a while, and at the end operation anyway will be
rescheduled to another thread pool, we can improve scalability by rescheduling
request processing immediately to a thread which is allowed to execute storage
operation. )
> Thin Client. Sql. Switch sql request processing to another thread pool
> ----------------------------------------------------------------------
>
> Key: IGNITE-25086
> URL: https://issues.apache.org/jira/browse/IGNITE-25086
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Reporter: Konstantin Orlov
> Assignee: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, all sql-related requests are processed on the thread assigned to
> client connection. Given that preparation sometimes may take a while, and at
> the end operation anyway will be rescheduled to another thread pool, we can
> improve scalability by rescheduling request processing immediately to a
> thread which is allowed to execute storage operation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
