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 <[email protected]> wrote: > Yes, will do. > > чт, 22 мар. 2018 г. в 1:05, Denis Magda <[email protected]>: > > > 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 <[email protected]> > > 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 <[email protected]>: > >> > >>> *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 < > >>> [email protected]> > >>> 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:[email protected]] > >>> > Sent: Wednesday, March 21, 2018 10:23 AM > >>> > To: dev <[email protected]> > >>> > 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 < > [email protected] > >>> > > >>> > 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 > >>> > > > >>> > > >>> > >> > > >
