Any status updates on Ignite 3.0?

[Glaviano, Anthony via user]

Greetings,

The last update for Ignite 3.0 that I can find is from November of 2022, 
although I see the project in GitHub has had continued activity.  My team is 
looking to start a new project using Ignite, and we were hoping to start with 
Ignite 3.0 since this will be a new greenfield project that we want to support 
for a long time into the future.  Is there any timeline/roadmap for v3.0 to 
make it to a general release candidate?  Or somewhere I can look to keep on top 
of its status?

Or would we be better off going with the latest v2.x release and hope to 
migrate to v3.0 at a later date?  Given the fundamental changes planned for 
v3.0, we were hoping to avoid having to do that.

Any advice or insights would be greatly appreciated.  Thanks.

--Anthony Glaviano



The information contained in this message is intended only for the recipient, 
and may be a confidential attorney-client communication or may otherwise be 
privileged and confidential and protected from disclosure. If the reader of 
this message is not the intended recipient, or an employee or agent responsible 
for delivering this message to the intended recipient, please be aware that any 
dissemination or copying of this communication is strictly prohibited. If you 
have received this communication in error, please immediately notify us by 
replying to the message and deleting it from your computer. S Global Inc. 
reserves the right, subject to applicable local law, to monitor, review and 
process the content of any electronic message or information sent to or from 
S Global Inc. e-mail addresses without informing the sender or recipient of 
the message. By sending electronic message or information to S Global Inc. 
e-mail addresses you, as the sender, are consenting to S Global Inc. 
processing any of your personal data therein.

Re: Question about REST/C++ client

[Stephen Darlington]

The easy answer to the "50 gets in parallel" is to use GetAll.

On Tue, 13 Feb 2024 at 09:54, Igor Sapego  wrote:

> 1. There is no such API. Seems like a weird error in documentation. We
> will fix it. If you want to make 50 gets in parallel, I think it's better
> to run 50 clients with the current API. You can use the same client too,
> but it may be slower, depending on how many nodes you have in a cluster.
> 2. What do you mean by increments? Do you mean getting value, modifying it
> and putting it back?
> 3. Atomics are faster in most cases (ReplaceIfEquals). Yes, there is a
> real overhead for transactions, though how big it is depends on the
> transaction isolation level.
>
> Best Regards,
> Igor
>
>
> On Thu, Feb 8, 2024 at 5:05 PM Louis C  wrote:
>
>>
>> Hello,
>>
>> I am trying to use/test Apache Ignite for a particular use case. For
>> background reference, my use case of Ignite is to do 100Ks (to begin with)
>> of "Gets" and of "increments" of values that will be stored in probably
>> multiple caches in Apache Ignite.
>> I read the Ignite documentation, but I couldn't figure out things in the
>> C++ API side.
>>
>>
>>1. I have read in the documentation
>>
>> 
>>
>> that
>>there is a "GetAsync" method in C++ client. But I could not find it in the
>>code. Is it a deprecated API ? If so, let's imagine I want to do multiple
>>calls in parallel (let's say 50 for instance), how can I achieve this ? 
>> Can
>>I just call multiple "Get"s in parallel in my threads without any problem 
>> ?
>>Must I create a client for each thread ? There does not seem to be 
>> anything
>>related to thread safety of these methods in the doc...
>>2. Does doing 100K "increments" of values in a cache seem achievable
>>on an Ignite cluster of a single node (let's say the CPU is a last gen i7
>>with 8 physical cores)? The problem that I have is that I have very good
>>performances (+100K "gets") using the batch methods of the Rest API, but 
>> no
>>batch method exist for "increments", and the overhead of each http call
>>cripples the performance to a few 1000s/s. What would be the "best" way of
>>achieving this (preferably in C++ or Rest API, but I am open to Java too 
>> )?
>>3. Related but a bit different : if I want to add a value to an
>>existing one in the store (doing an "increment"), would it be (in general)
>>faster to do it using the "transaction" mode or to use the
>>"ReplaceIfEquals" methods (in general I do not update the same values in
>>the same time) ? Is there a real overhead for transactions ?
>>
>>
>> Thanks in advance
>>
>> Louis
>>
>

Re: Question about REST/C++ client

[Igor Sapego]

1. There is no such API. Seems like a weird error in documentation. We will
fix it. If you want to make 50 gets in parallel, I think it's better to run
50 clients with the current API. You can use the same client too, but it
may be slower, depending on how many nodes you have in a cluster.
2. What do you mean by increments? Do you mean getting value, modifying it
and putting it back?
3. Atomics are faster in most cases (ReplaceIfEquals). Yes, there is a real
overhead for transactions, though how big it is depends on the transaction
isolation level.

Best Regards,
Igor


On Thu, Feb 8, 2024 at 5:05 PM Louis C  wrote:

>
> Hello,
>
> I am trying to use/test Apache Ignite for a particular use case. For
> background reference, my use case of Ignite is to do 100Ks (to begin with)
> of "Gets" and of "increments" of values that will be stored in probably
> multiple caches in Apache Ignite.
> I read the Ignite documentation, but I couldn't figure out things in the
> C++ API side.
>
>
>1. I have read in the documentation
>
> 
>
> that
>there is a "GetAsync" method in C++ client. But I could not find it in the
>code. Is it a deprecated API ? If so, let's imagine I want to do multiple
>calls in parallel (let's say 50 for instance), how can I achieve this ? Can
>I just call multiple "Get"s in parallel in my threads without any problem ?
>Must I create a client for each thread ? There does not seem to be anything
>related to thread safety of these methods in the doc...
>2. Does doing 100K "increments" of values in a cache seem achievable
>on an Ignite cluster of a single node (let's say the CPU is a last gen i7
>with 8 physical cores)? The problem that I have is that I have very good
>performances (+100K "gets") using the batch methods of the Rest API, but no
>batch method exist for "increments", and the overhead of each http call
>cripples the performance to a few 1000s/s. What would be the "best" way of
>achieving this (preferably in C++ or Rest API, but I am open to Java too )?
>3. Related but a bit different : if I want to add a value to an
>existing one in the store (doing an "increment"), would it be (in general)
>faster to do it using the "transaction" mode or to use the
>"ReplaceIfEquals" methods (in general I do not update the same values in
>the same time) ? Is there a real overhead for transactions ?
>
>
> Thanks in advance
>
> Louis
>