I would say that Ignite tends to work better with large numbers of small requests rather than a small number of big batches.
The Java API has the Data Streamer API to help, not sure if that’s in the C++ API. But I think smaller batches would help. I’ve not seen anyone request 18000 records in a single get command. Using colocated compute to avoid copying all those records over the network would improve performance. Or at least iterate over them using a scan or SQL query. Regards, Stephen > On 23 Apr 2021, at 15:24, jjimeno <jjim...@omp.com> wrote: > > Hello, and thanks for answering so quick > > Because, as you say, I should get a bigger throughput when increasing the > number of nodes. > > Of course I can't get the best of Ignite with this configuration, but I > would expect something similar to what I get writing: time decreasing while > nodes increase until the point that the single thread becomes the > bottleneck. > > Also, I wouldn't expect having better writing than reading times. > > Sorry, I don't have these values, but I'll try to repeat the tests to get > them. > > Josemari. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
