ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ivan Rakov <ivan.glu...@gmail.com>
Subject Re: Reconsider default WAL mode: we need something between LOG_ONLY and FSYNC
Date Thu, 12 Apr 2018 16:45:16 GMT

fsync() is really slow operation - it's the main reason why FSYNC mode 
is way slower than LOG_ONLY.
Fix includes extra fsyncs in necessary parts of code and nothing more. 
Every part is important - at the beginning of the thread I described why.

20% slow in benchmark doesn't mean than Ignite itself will become 20% 
slower. Benchmark replays only "data loading" scenario. It signals that 
maximum throughput with WAL enabled will be 20% slower. By the way, we 
already have option to disable WAL in runtime for the period of data 

Best Regards,
Ivan Rakov

On 11.04.2018 9:59, Dmitriy Setrakyan wrote:
> On Tue, Apr 10, 2018 at 11:57 PM, Ilya Suntsov <isuntsov@gridgain.com>
> wrote:
>> Dmitriy,
>> I've measured performance on the current master and haven't found any
>> problems with in-memory mode.
> Got it. I would still say that the performance drop is too big with
> persistence turned on. It seems like we did not just fix the bug, we also
> introduced some additional slow down there. I would investigate if we could
> optimize.

View raw message