Lucky,

Try enabling *enforceJoinOrder *parameter in JDBC connection string and let
us know the result.
Your JDBC connection string should look like this:
jdbc:ignite:thin://127.0.0.1?*enforceJoinOrder=true*

Denis

ср, 29 нояб. 2017 г. в 10:22, Lucky <[email protected]>:

> Have you come to a conclusion?
>
>
>
>
>
>
> At 2017-11-27 17:23:16, "Lucky" <[email protected]> wrote:
>
> Hi,Denis:
>     2.3 will be better than 2.2.
>     But the performance improvement is not obvious.
>     It took 2.5 seconds in single ignite  node ,and took 5 seconds in
> cluster(3 ignite nodes).
>
>     JDBC Client driver is worse than JDBC thin driver. it took about more
> 1 seconds.
>
>     Did there any other suggestiones?
>     Thanks.
>
>
> 2017-11-24 20:25,Denis Mekhanikov<[email protected]>
> <[email protected]> write:
>
> Hi!
>
> Please try running the same test on Ignite 2.3
> Also try changing to JDBC client driver
> <https://apacheignite-sql.readme.io/docs/jdbc-client-driver> and let us
> know the results.
>
> Denis
>
>

Reply via email to