Re: Re[4]: Performance of Ignite as key-value datastore. C++ Thin Client.

2021-02-03 Thread jjimeno
Thanks for updating!



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/


Re: Re[4]: Performance of Ignite as key-value datastore. C++ Thin Client.

2021-02-03 Thread Ilya Kasnacheev
Hello!

For the curious, the ticket is
https://issues.apache.org/jira/browse/IGNITE-14076

Regards,
-- 
Ilya Kasnacheev


пт, 29 янв. 2021 г. в 18:55, jjimeno :

> Ok... thanks!
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: Re[4]: Performance of Ignite as key-value datastore. C++ Thin Client.

2021-01-29 Thread jjimeno
Ok... thanks!



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/


Re[4]: Performance of Ignite as key-value datastore. C++ Thin Client.

2021-01-29 Thread Zhenya Stanilovsky


I suppose you can estimate time of loading 1.2 million keys with 2 ignite nodes 
right now.
Just load 1200 keys 1000 times, i believe assumed time would be similar.
And i hope you understand the difference between lsm\btree and 
embeded\distributed system.  
I can`t give you a fix date right now, may be next week will be clearer here.
 
thanks ! 
 
>First off, thanks to you and Zhenya for your support
>
>I'm afraid that's not easy, as key's data are unrelated.
>
>As we are in an evaluation phase, we would prefer to wait for the fix and
>perform single node benchmarking in the meanwhile... Instead of grouping
>keys, we might split the big transaction into several smaller ones, as
>Zhenya suggested, but that will not give us the real timings anyway.
>
>According to Zhenya's mail, the problem has been identified and it seems you
>can solve it. I know it's difficult, but.. could you give a rough fix date?
>
>
>
>--
>Sent from:  http://apache-ignite-users.70518.x6.nabble.com/