Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
References: <70ACF70D-348B-4A66-9E02-FB148D1F0485@apache.org> <1512549324113-0.post@n4.nabble.com>
In-Reply-To: <1512549324113-0.post@n4.nabble.com>
From: Dmitry Pavlov <dpavlov.spb@gmail.com>
Date: Wed, 06 Dec 2017 21:02:01 +0000
Message-ID: <CALUCNEuCqFVinSGtNkWLDaXKLUEmrqodsgf9jEUSE1sOm5N1aQ@mail.gmail.com>
Subject: Re: Time and scope for Apache Ignite 2.4
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary="001a1143fb22f2a179055fb24337"
archived-at: Wed, 06 Dec 2017 21:02:17 -0000

--001a1143fb22f2a179055fb24337
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

I suggest to include Andrey's change with WAL standalone thread, this will
speed up Ignite at least because CRC calcs goes to user threads instead of
one writer thread. This brings also resistence to thread interrupt and
other benefits.

Change, which I'm currently working on, is a direct IO
https://issues.apache.org/jira/browse/IGNITE-6341  If benchmarks will show
that memory usage decreased, I suggest to include this change also.

Sincerely,
Dmitry Pavlov

Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any company the author
might be affiliated with at the moment of writing.


=D1=81=D1=80, 6 =D0=B4=D0=B5=D0=BA. 2017 =D0=B3. =D0=B2 11:35, Yury Babak <=
y.chief@gmail.com>:

> Hi,
>
> As for ML - so far so good and from my point of view all mentioned tasks
> will be completed in this release.
>
> Regards,
> Yury
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

--001a1143fb22f2a179055fb24337--