[jira] [Commented] (IGNITE-20745) TableManager.tableAsync(int tableId) is slowing down thin clients

["Igor Sapego (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-20745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795722#comment-17795722 ] 

Igor Sapego commented on IGNITE-20745:
--------------------------------------

[~ibessonov] suggested to try the following quick fix:

Let's make the following call synchronous, and check if this will help:

At org.apache.ignite.internal.table.distributed.TableManager#tableAsyncInternal:
{code:java}
return orStopManagerFuture(schemaSyncService.waitForMetadataCompleteness(now))
                    .thenComposeAsync(unused -> inBusyLockAsync(busyLock, () -> {
...
{code}



> TableManager.tableAsync(int tableId) is slowing down thin clients
> -----------------------------------------------------------------
>
>                 Key: IGNITE-20745
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20745
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: 3.0.0-beta1
>            Reporter: Pavel Tupitsyn
>            Assignee: Igor Sapego
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>         Attachments: ItThinClientPutGetBenchmark.java
>
>
> Performance difference between embedded and client modes is affected considerably by the call to *IgniteTablesInternal#tableAsync(int id)*. This call has to be performed on every individual table operation.
> We should make it as fast as possible. Something like a dictionary lookup + quick check for deleted table.
> ||Part||Duration, us||
> |Network & msgpack|19.30|
> |Get table|14.29|
> |Get tuple & serialize|12.86|



--
This message was sent by Atlassian Jira
(v8.20.10#820010)