Ivan, Could we run Yardstick or YCSB benchmarks to see how the fixed LOG_ONLY affected the performance under the operational load (after the preloading part you're referring to is over)?
-- Denis On Thu, Apr 12, 2018 at 9:45 AM, Ivan Rakov <ivan.glu...@gmail.com> wrote: > Dmitriy, > > 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 > loading. > > Best Regards, > Ivan Rakov > > > On 11.04.2018 9:59, Dmitriy Setrakyan wrote: > >> On Tue, Apr 10, 2018 at 11:57 PM, Ilya Suntsov <isunt...@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. >> >> >
