xtern commented on PR #6921: URL: https://github.com/apache/ignite-3/pull/6921#issuecomment-3540474838
> I run different benchmarks several times and found a bit slowdown, of course it not relates to the current issue but: > > 1. can you confirm it ? > > 2. if it not expected - do we need an additional issue in such a case, wdyt ? > > > ``` > ignite-26149 > Benchmark (clusterSize) (fsync) (remote) Mode Cnt Score Error Units > SelectBenchmark.jdbcGet 1 false false avgt 10 128.480 ± 5.755 us/op > SelectBenchmark.jdbcGetScript 1 false false avgt 10 130.347 ± 3.216 us/op > > main > Benchmark (clusterSize) (fsync) (remote) Mode Cnt Score Error Units > SelectBenchmark.jdbcGet 1 false false avgt 10 118.385 ± 1.853 us/op > SelectBenchmark.jdbcGetScript 1 false false avgt 10 116.267 ± 3.229 us/op > ``` Unfortunately, my results fluctuate wildly; there may be a slight drop, but the result should be close to the thin client's. However, it's worth noting that in more realistic scenarios (with multiple nodes), the new driver's results significantly exceed those of the previous one. As I mentioned above, my results fluctuate wildly; I chose the best of the four runs for each branch: || name || nodes || result (new driver) || result (old driver) | SelectBenchmark.jdbcGet | 1 | 62.805 ± 3.196 | 60.556 ± 4.249 | | SelectBenchmark.jdbcGet | 3 | 80.577 ± 5.734 | 133.831 ± 10.380 | -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
