Ivan,
Great job. PR looks good.
This allocator in interleaved mode and passing `-XX:+UseNUMA` flag to jvm
> show promising results on yardstick benches. Technically, G1 is not a numa
> aware collector for java versions less than 14, but allocation of heap in
> interleaved mode shows good results
Andrey, thanks!
This allocator can be tested on every NUMA system.
Our runs show about 7-10 speedup, if we use allocattor with interleaved
strategy + -XX:+UseNUMA.
But unfortunately our yardstick benches doesn't use offheap a lot, usually
above one Gb.
We trying to do more benches with real data a
>> Our runs show about 7-10 speedup,
Sorry, typo 7-10% speedup
чт, 2 дек. 2021 г. в 12:01, Ivan Daschinsky :
> Andrey, thanks!
>
> This allocator can be tested on every NUMA system.
> Our runs show about 7-10 speedup, if we use allocattor with interleaved
> strategy + -XX:+UseNUMA.
> But unfortu
Slava,
Thank you for the comments.
> Maxim, the community must provide a reasonable time interval in order to
> notify all contributors and wait for updating all 3-rd party plugins.
This is not actually true. We must notify about changes as earlier as
possible and not only users but all the dev
Maxim,
> I don't think that we should wait for 3-rd party plugins to be updated
> this is an awful practice when the open-source product releases depend
> on some of the proprietary plugins
This makes no sense, sorry.
It is not that we depend on 3rd party plugins.
It is that *our users depend on
Pavel,
I don't understand why you are using *backwards compatibility* for
completely internal things. Why you are thinking in terms of users
usage when are talking about ignite-sys-cache but not thinking when
refactoring, for instance, all the checkpoint classes? Take a look at
the [1] issue. All
Hi, Igniters.
The release is blocked by the auth issue [1] discussed above. The
patch will be prepared at the nearest time.
I want to include the useful issue that adds the ability to configure
snapshot thread pool size if nobody minds.
[1] https://issues.apache.org/jira/browse/IGNITE-15966
[2]
Hello Maxim,
> I don't understand why you are using *backwards compatibility* for
completely internal things.
> Why you are thinking in terms of users usage when are talking about
ignite-sys-cache but not thinking when refactoring
First of all, we are talking about all plugin developers. It does n
Folks,
I've just published an article that lists some real-world use cases of
Ignite for high-performance computing. Some of you might be interested in
how the compute APIs are leveraged in practice:
https://www.gridgain.com/resources/blog/how-apache-ignite-empowers-high-performance-computing-real
I would like to formally announce code freeze for 2.12.0. Only
blockers are accepted to be included to the scope. [1]
We have one blocker issue [2] that will be fixed soon.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P3.Stabilization
[2] https://issues.a
Latest that I heard that it literally was never in use.
2021-11-29 19:44 GMT+03:00, Ivan Daschinsky :
> There is JNI library in ipc/shmem directory. It even compiles with minimal
> modification on modern gcc (9.3.0)
> But there is no script to build jar with native library.
>
> May be it is possib
So if nobody wants it to resurrect, maybe it is worth removing it?
пт, 3 дек. 2021 г. в 09:25, Ivan Pavlukhin :
> Latest that I heard that it literally was never in use.
>
> 2021-11-29 19:44 GMT+03:00, Ivan Daschinsky :
> > There is JNI library in ipc/shmem directory. It even compiles with
> min
Hi, igniters.
Recently I've discovered one fact
1. GridShmemCommunicationClient and all shmem functionality are broken
since 2.10. In master it is broken since August 2020. And nobody have
noticed it, only one thread in user list.
2. We have source code for native JNI library (that is shipped in
i
13 matches
Mail list logo
