Going off Francesca's results when implementing memory mapped for journal : https://issues.apache.org/jira/browse/ARTEMIS-906
Running mapped with no data sync will be of orders of magnitude on the write path. Sent from my iPhone > On 24 Mar 2017, at 01:53, Clebert Suconic <[email protected]> wrote: > > On Thu, Mar 23, 2017 at 9:38 PM Michael André Pearce < > [email protected]> wrote: > >> MemoryMapped for paging was actually the one I was more thinking to be >> beneficial. >> >> Afaik paging is rebuildable of server crash as essentially just memory >> spill from the heap? >> >> What I was thinking with memory mapped could give improved io at the >> expense of guaranteed disk persistence in server crash. But for paging I >> believe (please correct this assumption) this would be ok? > > > > It's the same as NIO actually in terms of guarantees. > > But it should save CPU on kernel calls. > > > > It will be awesome when people start usin new devices that are optimized > around mmap. > >> >> >> >> >> Sent from my iPhone >> >> On 24 Mar 2017, at 01:27, Clebert Suconic <[email protected]> >> wrote: >> >>>> It would make sense to implement Journal using Mappedfile.... >>> >>> >>> I meant Paging of course. >> > -- > Clebert Suconic
