>> * com.github.fommil.netlib:core:1.1.2 - not developed and archived since 2017. Last version released in 2013 [2] Moreover, this version is so outdated and JNI extension was so strangely made (linked to libgfortran3 for example), that native BLAS simply doesn't work. Always fallback option is used (f2jBLAS, and it is also outdated). There is a modern option -- https://github.com/luhenry/netlib, it is used in spark mllib.
I have run all tests successfully with it (with few lines changed, of course) using native blas (libopenblas on ubuntu 22.04) So it is possible to state that nobody has run it on native blas. So I have some concerns about existence of prod like installations with Ignite ML module пт, 11 авг. 2023 г. в 13:14, Николай Ижиков <nizhi...@apache.org>: > A few cents to let you know how abandoned ML module is. > > 1. Last valuable commit December 9, 2020 - > https://github.com/apache/ignite/commit/04f6a33851d9f7bd269a09fdc2c74485b1e01a8a > > 2. Dependencies and current versions of them: > > * com.dropbox.core:dropbox-core-sdk:2.1.1 current version is - 5.4.5 [1] > * com.github.fommil.netlib:core:1.1.2 - not developed and archived since > 2017. Last version released in 2013 [2] > * org.apache.commons:commons-rng-core:1.0 current version is 1.5 [3] > * com.zaxxer:SparseBitSet:1.0 current version is 1.2 [4] > * ai.catboost:catboost-prediction:0.24 current version is 1.2 [5] > * ai.h2o:h2o-genmodel:3.26.0.8 current version is 3.42.0.2 [6] > > ML community make a huge step forward since 2020. > So I doubt ML features and tools integrations works as expected nowadays. > Those type of Ignite features(abandoned or supported partially) has to be > in extensions. > > [1] https://github.com/dropbox/dropbox-sdk-java > [2] https://github.com/fommil/netlib-java > [3] https://commons.apache.org/proper/commons-rng/commons-rng-core/ > [4] https://github.com/brettwooldridge/SparseBitSet > [5] https://mvnrepository.com/artifact/ai.catboost/catboost-prediction > [6] https://mvnrepository.com/artifact/ai.h2o/h2o-genmodel > > > > > 11 авг. 2023 г., в 12:19, Kseniya Romanova <ksroman...@apache.org> > написал(а): > > > > As far as I know, the integration was removed from the Tensorflow side. > > > > On Thu, Aug 10, 2023 at 2:04 PM Andrey Mashenkov < > andrey.mashen...@gmail.com> > > wrote: > > > >> Ivan, > >> > >>> Actually, I haven't found any integration with tensorflow in AI code. > >> > >> Ok. You are right. > >> Tensorflow is mentioned in docs: docs/_docs/setup.adoc. > >> > >> Adapters may require compilation time dependencies, but these > dependencies > >> shouldn't be part or release package, > >> regardless whether the ML module is a part of Ignite or extensions. > WDYT? > >> > >> On Thu, Aug 10, 2023 at 1:36 PM Ivan Daschinsky <ivanda...@gmail.com> > >> wrote: > >> > >>> Actually, I haven't found any integration with tensorflow in AI code. > >>> Actually, all integrations are some adapters that allow to load > >> pretrained > >>> models (h2o, catboost etc.) > >>> > >>> чт, 10 авг. 2023 г. в 13:08, Ivan Daschinsky <ivanda...@gmail.com>: > >>> > >>>> I am personally for moving to extensions. Alex has already mentioned > >> all > >>>> the reasons why it should be done and all of them are quite important. > >>>> The module seems to be quite independent and there is no problem to > >> move > >>>> it to ignite-extensions. > >>>> So I am +1 for moving to ignite-extensions. > >>>> > >>>> > >>>> чт, 10 авг. 2023 г. в 12:45, Kseniya Romanova <ksroman...@apache.org > >: > >>>> > >>>>>> > >>>>>> do you know anyone who uses it? > >>>>> > >>>>> I know some teams, who do. At the last Ignite Summit we had a talk > >>>>> featuring Ml module (from the Groovy community). > >>>>> Anyway, We need here the module maintainer opinion > >>>>> + Alex > >>>>> > >>>>> On Wed, Aug 9, 2023 at 3:38 PM Andrey Mashenkov < > >>>>> andrey.mashen...@gmail.com> > >>>>> wrote: > >>>>> > >>>>>> -1 for removal. > >>>>>> 0 for relocation > >>>>>> > >>>>>> imho, TC resources and module size aren't good arguments for > >>>>>> removal/moving. > >>>>>> ML tests could be run nightly. > >>>>>> ML module contains few integrations (with TensorFlow and other), > >> these > >>>>>> optional integrations are wighty and could be moved to extension, > >>>>>> but core functionality still can be left untouched if it is highly > >>>>> coupled > >>>>>> with core Ignite and moving to extension is hard. > >>>>>> > >>>>>> > >>>>>> On Wed, Aug 9, 2023 at 3:22 PM Anton Vinogradov <a...@apache.org> > >>> wrote: > >>>>>> > >>>>>>> +1 to relocation > >>>>>>> > >>>>>>> On Wed, Aug 9, 2023 at 3:09 PM Alex Plehanov < > >>> plehanov.a...@gmail.com > >>>>>> > >>>>>>> wrote: > >>>>>>> > >>>>>>>> Pavel, do you know anyone who uses it? > >>>>>>>> > >>>>>>>> Looks like it isn't used at all (no questions on mail lists, no > >>>>>>>> tickets), but we spend developers time to build module with > >> every > >>>>>>>> Ignite rebuild, we spend users traffic to download module (ML > >> with > >>>>>>>> dependencies takes about 1/4 of our binary release package size) > >>> and > >>>>>>>> we spend team-city resources to test module. > >>>>>>>> > >>>>>>>> +1 for removing or moving to extensions. > >>>>>>>> > >>>>>>>> ср, 9 авг. 2023 г. в 14:19, Pavel Tupitsyn < > >> ptupit...@apache.org > >>>> : > >>>>>>>>> > >>>>>>>>> Does it have any outstanding issues? A stable and useful > >> module > >>>>>> should > >>>>>>>> not > >>>>>>>>> be removed just because it does not evolve. > >>>>>>>>> > >>>>>>>>> On Wed, Aug 9, 2023 at 1:46 PM Ivan Daschinsky < > >>>>> ivanda...@apache.org > >>>>>>> > >>>>>>>> wrote: > >>>>>>>>> > >>>>>>>>>> Igniters, seems that this module is completely abandoned for > >>>>> more > >>>>>>> than > >>>>>>>> 2 > >>>>>>>>>> years. But it is enormous and it seems that nobody wants to > >>> take > >>>>>> care > >>>>>>>> of > >>>>>>>>>> it. I suggest just removing it or moving it to extensions > >> (as > >>>>>>> option). > >>>>>>>>>> WDYT? > >>>>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> Best regards, > >>>>>> Andrey V. Mashenkov > >>>>>> > >>>>> > >>>> > >>>> > >>>> -- > >>>> Sincerely yours, Ivan Daschinskiy > >>>> > >>> > >>> > >>> -- > >>> Sincerely yours, Ivan Daschinskiy > >>> > >> > >> > >> -- > >> Best regards, > >> Andrey V. Mashenkov > >> > > -- Sincerely yours, Ivan Daschinskiy
