Re: Exploiting GP GPUs in Ignite ML

Yes, as one of possible options. ср, 21 марта 2018, 20:53 Igor Rudyak : > You mean utilizing JCuda for CPU bound ML tasks? > > Igor > > On Wed, Mar 21, 2018 at 10:45 AM, Andrey Kuznetsov > wrote: > > > Hi, Igniters! > > > > Machine Learning algorithms

[GitHub] ignite pull request #3676: IGNITE-8005: Added example

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/3676 IGNITE-8005: Added example Fixed a few points in other SVM files You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: readme.io weird interface element

Thanks Petr. I'll look into it. On Wed, Mar 21, 2018 at 12:44 AM, Petr Ivanov wrote: > Filed https://issues.apache.org/jira/browse/IGNITE-8003 > > > > > On 20 Mar 2018, at 21:14, Prachi Garg wrote: > > > > Hi Petr, Denis, > > > > Sorry missed the

Re: IGNITE-6827 - Review needed.

Hi Alexei, > Pavel Tupitsyn, could you lend a hand to help completing .NET part (two new public API methods are added as a part of working on [3], java code in branch [2]) Please file a separate ticket for .NET changes. I would like to help, but maybe some time later. No need to delay your

[GitHub] ignite pull request #3675: IGNITE-7983: NPE fix.

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3675 IGNITE-7983: NPE fix. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-7983 Alternatively you can

Re: IGNITE-3999 review

Dmitry, Since the last TC test run has been done almost 2 months ago I decided to run it again since lot of changes were introduced. I will let you know when tests are finished. Thanks, Amir

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

+1 for the fix of LOG_ONLY On Wed, Mar 21, 2018 at 11:23 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > +1 for fixing LOG_ONLY to enforce corruption safety given the provided > performance results. > > 2018-03-21 18:20 GMT+03:00 Vladimir Ozerov : > > > +1 for

[GitHub] ignite pull request #3674: IGNITE-7682: CPP: Fixed constant for the LocalSiz...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/3674 IGNITE-7682: CPP: Fixed constant for the LocalSize operation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Nodes which started in separate JVM couldn't stop properly (in tests)

Hi Nickolay, it seems we have lazy consesus here. Failures: tests 11 suites 1, all these tests are failed in master. Could you merge? Sincerely, Dmitriy Pavlov пт, 16 мар. 2018 г. в 18:29, Nikolay Izhikov : > Hello, Guys. > > I'm reviewed changes and it looks good to

RE: Apache Ignite nightly release builds

The link to build artifacts requires a Team City login. Is there a public access location? *From:* Petr Ivanov [mailto:mr.wei...@gmail.com] *Sent:* Wednesday, March 21, 2018 10:59 PM *To:* dev ; u...@ignite.apache.org *Subject:* Re: Apache Ignite nightly release builds

Re: Apache Ignite nightly release builds

Hi Raymond, You could sign up using valid email address. Please write to @dev list if link still is not available. Sincerely, Dmitriy Pavlov ср, 21 мар. 2018 г. в 22:34, Raymond Wilson : > The link to build artifacts requires a Team City login. Is there a public >

Re: Exploiting GP GPUs in Ignite ML

You mean utilizing JCuda for CPU bound ML tasks? Igor On Wed, Mar 21, 2018 at 10:45 AM, Andrey Kuznetsov wrote: > Hi, Igniters! > > Machine Learning algorithms consume much computational resources. So I'm > curious whether it's possible to exploit General Purpose GPUs in

Re: IGNITE-3999 review

Hi Amir, Thank you for your contribution. Could you share link to Teamcity run all? Sincerely Dmitry Pavlov ср, 21 мар. 2018 г., 21:23 Amir Akhmedov : > Hi Team, > > Can anybody review https://github.com/apache/ignite/pull/3444 please? > > Thanks, > Amir >

Exploiting GP GPUs in Ignite ML

Hi, Igniters! Machine Learning algorithms consume much computational resources. So I'm curious whether it's possible to exploit General Purpose GPUs in Ignite? Did somebody think about this? -- Best regards, Andrey Kuznetsov.

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

+1 for fixing LOG_ONLY to enforce corruption safety given the provided performance results. 2018-03-21 18:20 GMT+03:00 Vladimir Ozerov : > +1 for accepting drop in LOG_ONLY. 7% is not that much and not a drop at > all, provided that we fixing a bug. I.e. should we implement

IGNITE-3999 review

Hi Team, Can anybody review https://github.com/apache/ignite/pull/3444 please? Thanks, Amir

Re: Move documentation from readme.io to GitHub pages

We can store the project (Markdown & Docusaurus config files) in Git, use Docusaurus to build html, and upload them to Ignite website. On Tue, Mar 20, 2018 at 10:29 PM, Dmitriy Setrakyan wrote: > Does docusaurus work with GitHub only, or with Git in general? In Apache >

Re: Stop nodes after test by default - IGNITE-6842

Hi Nikolai, will you have time to merge this change? вт, 20 мар. 2018 г. в 11:52, Dmitry Pavlov : > Dmitriy, thank you for review. This fix should do our tests more stable. > > Nikolay, could you please merge? > > вт, 20 мар. 2018 г. в 11:49, Dmitriy Govorukhin < >

Re: Apache Ignite nightly release builds

OK, I guess I can present renewed Apache Ignite Nightly Releases. Link to artifacts of the latest successful build: https://ci.ignite.apache.org/viewLog.html?buildId=lastSuccessful=Releases_NightlyRelease_RunApacheIgniteNightlyRelease=artifacts

[GitHub] ignite pull request #3666: IGNITE-7712 Add flag IGNITE_SQL_LAZY_RESULT_SET f...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/3666 IGNITE-7712 Add flag IGNITE_SQL_LAZY_RESULT_SET for setting default …value of SqlFieldsQuery.lazy You can merge this pull request into a Git repository by running: $ git pull

welcome

Hello Ignite Community! My name isAndrei. I want to contribute to Apache Ignite and want to start with this issue - IGNITE-7902but I can't assign it to me, my JIRA usernameaealeksandrov. Any help on this will be appreciated. Thanks!

Re: IGNITE-6827 - Review needed.

Hi Alexei , Thank you for contribution, unfortunately there is too much tests failed there: .NET is broken Ignite Platform .NET Long Running [ tests 3 ] CachePartitionedNearEnabledTest.TestTransactionScopeMultiCache(True) CachePartitionedTest.TestTransactionScopeMultiCache(True)

Re: welcome

Hi Andrei, Thank you for your interest in Apache Ignite. Could we double-check you username? Is it aealeksandrov ? Sincerely, Dmitriy Pavlov ср, 21 мар. 2018 г. в 13:18, Andrei Aleksandrov : > Hello Ignite Community! > > My name isAndrei. I want to contribute to

[GitHub] ignite pull request #3667: Ignite 2.4.4

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/3667 Ignite 2.4.4 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.4.4 Alternatively you can review and apply

Re: readme.io weird interface element

Filed https://issues.apache.org/jira/browse/IGNITE-8003 > On 20 Mar 2018, at 21:14, Prachi Garg wrote: > > Hi Petr, Denis, > > Sorry missed the message. Petr, please feel free to create a ticket. > > Thanks, > -Prachi > > > On Mon, Mar 19, 2018 at 8:24 PM, Petr Ivanov

[jira] [Created] (IGNITE-8004) Failed to find class BaselineTopology

Anton Kalashnikov created IGNITE-8004: - Summary: Failed to find class BaselineTopology Key: IGNITE-8004 URL: https://issues.apache.org/jira/browse/IGNITE-8004 Project: Ignite Issue Type:

Re: 2 phase waiting for partitions release

For now, I think the two-phase await is the only option. After the fix is prototyped we need to benchmark and check what is the impact of this change on PME timing. 2018-03-20 18:09 GMT+03:00 Dmitry Pavlov : > Hi Igniters, > > I prefer option 1 because throwing any

IGNITE-6827 - Review needed.

Igniters, I prepared rather important patch [1] related to grid stability and need a review and some help to finish it. Semyon Boikov, could you please take a look on patch code ? [2] Pavel Tupitsyn, could you lend a hand to help completing .NET part (two new public API methods are added as a

[GitHub] ignite pull request #3664: IGNITE-7969 Fixed failure of failure of IgniteTop...

GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/3664 IGNITE-7969 Fixed failure of failure of IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidatorWithCacheGroup You can merge this pull request into a Git repository by running:

[jira] [Created] (IGNITE-8003) Dead documentation interface element

Peter Ivanov created IGNITE-8003: Summary: Dead documentation interface element Key: IGNITE-8003 URL: https://issues.apache.org/jira/browse/IGNITE-8003 Project: Ignite Issue Type: Bug

Re: IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts

Hi Yakov, Do the proposed changes look good to you? Thanks, Alexey -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[GitHub] ignite pull request #3665: ignite-8004 set compatibilityMode to true in coll...

GitHub user akalash opened a pull request: https://github.com/apache/ignite/pull/3665 ignite-8004 set compatibilityMode to true in collectGridNodeData You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #1485: IGNITE-4584 Async API: Tests refactoring to use n...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/1485 ---

[GitHub] ignite pull request #967: IGNITE-3694 IgfsLocalSecondaryFileSystemDualAsyncS...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/967 ---

[GitHub] ignite pull request #1446: IGNITE-4580 Async API: IgniteCompute refactoring

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/1446 ---

[GitHub] ignite pull request #969: IGNITE-3632 IGFS: Use task execution for PARTITION...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/969 ---

[GitHub] ignite pull request #987: IGNITE-3167 Hadoop: restore external execution.

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/987 ---

[GitHub] ignite pull request #1647: IGNITE-3018 Performance tuning of the Rendezvous ...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/1647 ---

[GitHub] ignite pull request #1460: IGNITE-4582 Async API: IgniteFileSystem refactori...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/1460 ---

[GitHub] ignite pull request #1452: IGNITE-4581: Async API: IgniteCache refactoring

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/1452 ---

[GitHub] ignite pull request #1462: IGNITE-4583 Async API: Other components refactori...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/1462 ---

[jira] [Created] (IGNITE-8005) [ML] Adopt SVM Linear MultiClass Classification Example to the new Partitioned Dataset

Aleksey Zinoviev created IGNITE-8005: Summary: [ML] Adopt SVM Linear MultiClass Classification Example to the new Partitioned Dataset Key: IGNITE-8005 URL: https://issues.apache.org/jira/browse/IGNITE-8005

[GitHub] ignite pull request #3668: IGNITE-6711 DataRegionMetrics#totalAllocatedPages...

GitHub user alamar opened a pull request: https://github.com/apache/ignite/pull/3668 IGNITE-6711 DataRegionMetrics#totalAllocatedPages is not valid after PDS restart You can merge this pull request into a Git repository by running: $ git pull

Re: welcome

Hi Dmitry, This one is that I see in my profile: Username: aealeksandrov Full name: Andrey Aleksandrov Email: aealexsandrov at gmail dot com Best regards, Andrei Aleksandrov 21.03.2018 13:31, Dmitry Pavlov пишет: Hi Andrei, Thank you for your interest in Apache Ignite. Could we

[GitHub] ignite pull request #1268: IGNITE-3640 IGFS: Local secondary: Investigate wh...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/1268 ---

[GitHub] ignite pull request #1159: IGNITE-4054 Add debug to trace HadoopMapReducePla...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/1159 ---

[GitHub] ignite pull request #1294: IGNITE-4263 Hadoop: abstract out offheap/heap mem...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/1294 ---

[GitHub] ignite pull request #1026: IGNITE-3611 IGFS: Merge listPaths and listFiles o...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/1026 ---

[GitHub] ignite pull request #2233: IGNITE-5679: add JDBC example

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/2233 ---

[GitHub] ignite pull request #822: GG-11133 TTL should be tracked in off-heap page st...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/822 ---

Re: welcome

Andrei, Welcome to the community! Added you to the contributors list. 2018-03-21 15:04 GMT+03:00 Andrei Aleksandrov : > Hi Dmitry, > > This one is that I see in my profile: > > Username: >aealeksandrov > > Full name: >Andrey Aleksandrov > > Email: >

[GitHub] ignite pull request #1974: IGNITE-4892 Support DML for thin client based JDB...

Github user tledkov-gridgain closed the pull request at: https://github.com/apache/ignite/pull/1974 ---

Re: Ignite Direct I/O plugin description added to wiki

Dmitriy, Thanks for updating the WAL section. Now it makes total sense to me. As for the page with JNA projects, let's get added there! Could you contact the owners? -- Denis On Wed, Mar 21, 2018 at 9:27 AM, Dmitry Pavlov wrote: > Denis, > > one more thing, can/should

[GitHub] ignite pull request #3676: IGNITE-8005: Added example

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3676 ---

[jira] [Created] (IGNITE-8009) SQL local query to a cache with queryParallelism>1 doesn't use index

Pavel Vinokurov created IGNITE-8009: --- Summary: SQL local query to a cache with queryParallelism>1 doesn't use index Key: IGNITE-8009 URL: https://issues.apache.org/jira/browse/IGNITE-8009 Project:

[jira] [Created] (IGNITE-8006) Starting multiple caches inhibits exchange process on joining node

Vladislav Pyatkov created IGNITE-8006: - Summary: Starting multiple caches inhibits exchange process on joining node Key: IGNITE-8006 URL: https://issues.apache.org/jira/browse/IGNITE-8006

[GitHub] ignite pull request #3669: Ignite-2.3.3.b2

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/3669 Ignite-2.3.3.b2 for test purposes You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.3.3.b2 Alternatively you

[GitHub] ignite pull request #3670: Separate cache for non-collocated IgniteSet (TC r...

GitHub user xtern opened a pull request: https://github.com/apache/ignite/pull/3670 Separate cache for non-collocated IgniteSet (TC run) You can merge this pull request into a Git repository by running: $ git pull https://github.com/xtern/ignite IGNITE-7823 Alternatively you

[GitHub] ignite pull request #3672: IGNITE-6113 Backport to 2.4.4

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3672 IGNITE-6113 Backport to 2.4.4 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-13616-2.4.4 Alternatively you

[GitHub] ignite pull request #3662: IGNITE-6113 Backport to 2.4.3.b1

Github user Jokser closed the pull request at: https://github.com/apache/ignite/pull/3662 ---

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

I've attached benchmark results to the JIRA ticket. We observe ~7% drop in "fair" LOG_ONLY_SAFE mode, independent of WAL compaction enabled flag. It's pretty significant drop: WAL compaction itself gives only ~3% drop. I see two options here: 1) Change LOG_ONLY behavior. That implies that

[GitHub] ignite pull request #3671: IGNITE-7852: Supported username/password authenti...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/3671 IGNITE-7852: Supported username/password authentication for ODBC You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

Hi, I think option 1 is better. As Val said any mode that allows corruption does not make much sense. What Ivan mentioned here as drop, in relation to old mode DEFAULT (FSYNC now), is still significant perfromance boost. Sincerely, Dmitriy Pavlov ср, 21 мар. 2018 г. в 17:56, Ivan Rakov

Re: Move documentation from readme.io to GitHub pages

On Wed, Mar 21, 2018 at 9:27 PM, Prachi Garg wrote: > We can store the project (Markdown & Docusaurus config files) in Git, use > Docusaurus to build html, and upload them to Ignite website. > Sounds good!

[jira] [Created] (IGNITE-8008) Web console: Add a link to the SQL documentation in Notebook title

Pavel Konstantinov created IGNITE-8008: -- Summary: Web console: Add a link to the SQL documentation in Notebook title Key: IGNITE-8008 URL: https://issues.apache.org/jira/browse/IGNITE-8008

Re: IGNITE-3999 review

Dmitry, TeamCity RunAll completed but the results look awkward. Almost all test suites marked as failed. I noticed the same behavior for other builds though. If you don't mind could you please check is it alright and let me know?

Subject: new committer: Dmitry Pavlov

The Project Management Committee (PMC) for Apache Ignite has invited Dmitry Pavlov to become a committer and we are pleased to announce that he has accepted. Dmitriy is an active member of the Apache Ignite community. He is an author of the great 'Make TeamCity Green Again' initiative [1] which

[jira] [Created] (IGNITE-8007) We should treat as empty any partition as empty if it doesn't have any data

Eduard Shangareev created IGNITE-8007: - Summary: We should treat as empty any partition as empty if it doesn't have any data Key: IGNITE-8007 URL: https://issues.apache.org/jira/browse/IGNITE-8007

[GitHub] ignite pull request #3677: IGNITE-8007 We should treat as empty any partitio...

GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/3677 IGNITE-8007 We should treat as empty any partition as empty if it doe… …sn't have any data You can merge this pull request into a Git repository by running: $ git pull

Re: Ignite Direct I/O plugin description added to wiki

Hi Igniters, I've updated page with more detailed info about WAL and NativeIO, added references to system properties. Denis, thank you for noticing unclear section. Sincerely, Dmitriy Pavlov ср, 21 мар. 2018 г. в 2:18, Raymond Wilson : > Denis, > > Thanks for the

Re: Ignite Direct I/O plugin description added to wiki

Denis, one more thing, can/should we mention Ignite Direct IO plugin in list of project using JNA here: https://github.com/java-native-access/jna Sincerely, Dmitriy Pavlov ср, 21 мар. 2018 г. в 1:59, Denis Magda : > *Dmitriy*, thanks. Astonishing job! We'll add a section to

[GitHub] ignite pull request #3673: IGNITE-7990 Integrate MLP with partition based da...

GitHub user dmitrievanthony opened a pull request: https://github.com/apache/ignite/pull/3673 IGNITE-7990 Integrate MLP with partition based dataset You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC

+1 for accepting drop in LOG_ONLY. 7% is not that much and not a drop at all, provided that we fixing a bug. I.e. should we implement it correctly in the first place we would never notice any "drop". I do not understand why someone would like to use current broken mode. On Wed, Mar 21, 2018 at

[GitHub] ignite pull request #3663: ignite-7989 returned ConcurrentHashMap8 for backw...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3663 ---