ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Ignite Direct I/O plugin description added to wiki
Date Sun, 25 Mar 2018 14:10:58 GMT
Nice!

On Sun, Mar 25, 2018 at 2:57 PM, Dmitry Pavlov <dpavlov.spb@gmail.com>
wrote:

> Hi Igniters,
>
> Apache Ignite Entry was added to the projects list by JNA developers.
>
> Now Apache Ignite is mentioned in main Java Native Access Readme.MD (
> https://github.com/java-native-access/jna ), and link to Ignite site is
> also available there.
>
> Sincerely,
> Dmitriy Pavlov
>
>
> сб, 24 мар. 2018 г. в 3:33, Denis Magda <dmagda@apache.org>:
>
> > Dmitriy, Prachi,
> >
> > Thanks to both of you for the development and documentation of the
> feature.
> > I've added a reference from readme to Direct I/O section on wiki so that
> > people can learn even more about the capability.
> >
> > --
> > Denis
> >
> > On Fri, Mar 23, 2018 at 2:34 PM, Dmitry Pavlov <dpavlov.spb@gmail.com>
> > wrote:
> >
> > > Hi Prachi,
> > >
> > > Yes, it's a great description.
> > >
> > > I'm impressed by how informative and short you managed to make it.
> > >
> > > Thank you!
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > сб, 24 мар. 2018 г. в 0:29, Prachi Garg <pgarg@gridgain.com>:
> > >
> > >> Dmitriy,
> > >>
> > >> I have documented the Direct I/O plugin. Please review [1] and provide
> > >> comments/feedback in the ticket [2].
> > >>
> > >> [1]
> > >> https://apacheignite.readme.io/v2.4/docs/durable-memory-
> > >> tuning#section-enabling-direct-i-o
> > >>
> > >> [2] https://issues.apache.org/jira/browse/IGNITE-7466
> > >>
> > >>
> > >> -Prachi
> > >>
> > >> On Wed, Mar 21, 2018 at 11:22 PM, Dmitry Pavlov <
> dpavlov.spb@gmail.com>
> > >> wrote:
> > >>
> > >> > Yes, will do.
> > >> >
> > >> > чт, 22 мар. 2018 г. в 1:05, Denis Magda <dmagda@apache.org>:
> > >> >
> > >> > > 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 <
> > dpavlov.spb@gmail.com
> > >> >
> > >> > > wrote:
> > >> > >
> > >> > >> 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 <dmagda@apache.org>:
> > >> > >>
> > >> > >>> *Dmitriy*, thanks. Astonishing job! We'll add a section
to the
> > >> durable
> > >> > >>> memory tuning page and refer to the wiki for more details:
> > >> > >>> https://issues.apache.org/jira/browse/IGNITE-7466
> > >> > >>>
> > >> > >>> Please clarify the following:
> > >> > >>>
> > >> > >>> > Direct I/O mode can't be enabled for Write Ahead
Log files.
> > >> However,
> > >> > >>> when
> > >> > >>> > working with plugin, WAL manager applies advising
Linux
> systems
> > do
> > >> > not
> > >> > >>> > store the data of the file in page cache as they
are not
> > required.
> > >> > >>>
> > >> > >>>
> > >> > >>> For me, it means that WAL always goes through the operating
> system
> > >> I/O
> > >> > >>> calls. Nothing changes for the WAL. However, I'm not
sure what
> you
> > >> > meant
> > >> > >>> to
> > >> > >>> explain by saying "when working with the plugin (Direct
I/O) WAL
> > >> > manager
> > >> > >>> applies...". Could you rephrase it to bring more clarity?
> > >> > >>>
> > >> > >>> *Raymond,*
> > >> > >>>
> > >> > >>>
> > >> > >>> If Direct I/O is enabled by default it will bring down
the
> > >> performance
> > >> > of
> > >> > >>> read-intensive application because, as Dmitry says, the
reads
> > bypass
> > >> > page
> > >> > >>> cache. So, I would recommend using it for write-intensive
> > workloads
> > >> > and,
> > >> > >>> probably, for mixed-workloads depending on the reads
and writes
> > >> rate.
> > >> > >>>
> > >> > >>> --
> > >> > >>> Denis
> > >> > >>>
> > >> > >>>
> > >> > >>> On Tue, Mar 20, 2018 at 2:29 PM, Raymond Wilson <
> > >> > >>> raymond_wilson@trimble.com>
> > >> > >>> wrote:
> > >> > >>>
> > >> > >>> > Looks good!
> > >> > >>> >
> > >> > >>> > Is there any reason why this should not be a default
setting
> if
> > it
> > >> > >>> > gracefully downgrades to non-Direct IO if not supported
by the
> > OS?
> > >> > >>> >
> > >> > >>> > Thanks,
> > >> > >>> > Raymond.
> > >> > >>> >
> > >> > >>> > -----Original Message-----
> > >> > >>> > From: Dmitriy Setrakyan [mailto:dsetrakyan@apache.org]
> > >> > >>> > Sent: Wednesday, March 21, 2018 10:23 AM
> > >> > >>> > To: dev <dev@ignite.apache.org>
> > >> > >>> > Subject: Re: Ignite Direct I/O plugin description
added to
> wiki
> > >> > >>> >
> > >> > >>> > Thanks Dmitry, awesome work!
> > >> > >>> >
> > >> > >>> > On Wed, Mar 21, 2018 at 12:21 AM, Dmitry Pavlov
<
> > >> > dpavlov.spb@gmail.com
> > >> > >>> >
> > >> > >>> > wrote:
> > >> > >>> >
> > >> > >>> > > Hi Igniters,
> > >> > >>> > >
> > >> > >>> > > I've added description of new plugin for Direct
I/O for
> native
> > >> > >>> > > persistence (
> > >> > >>> > > https://issues.apache.org/jira/browse/IGNITE-6341)
 to wiki
> > >> > >>> > > https://cwiki.apache.org/confluence/display/IGNITE/
> > >> > >>> > >
> > Ignite+Persistent+Store+-+under+the+hood#IgnitePersistentStore-
> > >> > >>> > > underthehood-DirectI/O
> > >> > >>> > >
> > >> > >>> > >
> > >> > >>> > > SIncerely,
> > >> > >>> > > Dmitriy Pavlov
> > >> > >>> > >
> > >> > >>> >
> > >> > >>>
> > >> > >>
> > >> > >
> > >> >
> > >>
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message