Have a look at [1], there is a POC linked [2]
[1] https://www.mail-archive.com/dev@ignite.apache.org/msg53182.html
[2] https://github.com/scottmf/graalvm-ignite
On Fri, Mar 1, 2024 at 8:01 AM Kramer wrote:
> I believe this is not supported with Ignite 2.x due to Native Buffer
> access. It will
I believe this is not supported with Ignite 2.x due to Native Buffer access. It will only be part of Ignite 3 which is still Beta.I haven't tested it myself though, so my comment should be confirmed by others.On 2/29/24, 14:14 Dinakar Devineni wrote:
Hi,
Has anyone tried
You would need to test it to find out.
On Thu, 29 Feb 2024 at 12:03, Dinakar Devineni wrote:
> Does that even work with the newer versions of ignite?
>
>
>
> *From: *Stephen Darlington
> *Sent: *Thursday, February 29, 2024 4:45 AM
> *To: *user@ignite.apache.org
> *Subject: *Re: Control
Hi, Has anyone tried spring native image with ignite? If so is it efficient and what are the pros and cons.Spring Native documentation ThanksDina
Does that even work with the newer versions of ignite? From: Stephen DarlingtonSent: Thursday, February 29, 2024 4:45 AMTo: user@ignite.apache.orgSubject: Re: Control center open source The community used to maintain Web Console. You might be able to get that running again? On Thu, 29 Feb
You can add a filter to your log exporter, so that only the metrics you're
interested in are shared.
"Expensive" might be the wrong word to explain the overhead in enabling
metrics. Enabling metrics does use more resources than not, but it's
usually worth it. In general, you can't put a system
The community used to maintain Web Console. You might be able to get that
running again?
On Thu, 29 Feb 2024 at 04:08, Dinakar Devineni wrote:
> Hi ,
>
> Is there ant grid gain control center open source alternative.
> Is there any other community project?
>
> Thanks
> Dina
>
There's not much overhead simply by enabling SQL, but there's obviously a
cost to maintaining any indexes you create. Normally the cost of
maintaining those indexes is more than offset by improvements in query
performance. But the only real way to tell for your use case is to
benchmark it.
On
