From 11e88b701a5389d6fb578c85d0349ae9f2293d4f Mon Sep 17 00:00:00 2001 From: Jonas Hahnfeld Date: Tue, 7 Jan 2025 16:51:18 +0100 Subject: [PATCH] [ntuple] Remove outdated comment We require buffered writing with the RNTupleParallelWriter because of its better scalability and less fragmented output files, see also https://github.com/root-project/root/pull/14939. --- tree/ntuple/v7/src/RNTupleParallelWriter.cxx | 3 --- 1 file changed, 3 deletions(-) diff --git a/tree/ntuple/v7/src/RNTupleParallelWriter.cxx b/tree/ntuple/v7/src/RNTupleParallelWriter.cxx index 9ce6c1b81ae7a..143ef581357a4 100644 --- a/tree/ntuple/v7/src/RNTupleParallelWriter.cxx +++ b/tree/ntuple/v7/src/RNTupleParallelWriter.cxx @@ -182,9 +182,6 @@ std::shared_ptr ROOT::Experimental::RNTu std::lock_guard g(fMutex); auto model = fModel->Clone(); - - // TODO: Think about honoring RNTupleWriteOptions::SetUseBufferedWrite(false); this requires synchronization on every - // call to CommitPage() *and* preparing multiple cluster descriptors in parallel! auto sink = std::make_unique(std::make_unique(*fSink, fSinkMutex)); // Cannot use std::make_shared because the constructor of RNTupleFillContext is private. Also it would mean that the