From d0d53f68dfe0013a111870072324a08c9be60aca Mon Sep 17 00:00:00 2001 From: richterm Date: Sat, 6 Jun 2009 23:18:43 +0000 Subject: [PATCH] Disable writing of individual ESD files for the different origins. It was the first attempt and has been a debugging feature after proper implementation of ESD merging. Writing of individual files has now been identified to cause increasing memory consumption and slow down of reconstruction. --- HLT/rec/AliHLTEsdManagerImplementation.cxx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/HLT/rec/AliHLTEsdManagerImplementation.cxx b/HLT/rec/AliHLTEsdManagerImplementation.cxx index 3f0df73ec5e..b4ac8670c3b 100644 --- a/HLT/rec/AliHLTEsdManagerImplementation.cxx +++ b/HLT/rec/AliHLTEsdManagerImplementation.cxx @@ -249,6 +249,14 @@ int AliHLTEsdManagerImplementation::AliHLTEsdListEntry::WriteESD(AliESDEvent* pS { // see header file for class documentation int iResult=0; + + // Matthias 2009-06-06: writing of individual ESD files for the different origins was a + // first attempt when functionality was missing in the AliRoot framework and remained as + // debugging feature. ESD merging is now implemented and data written to the hltEsd, so + // the feature is now disabled because it causes increasing memory consumption. Presumably + // not because of a memory leak but the way the internal TTree is used and kept in memory. + return 0; + #ifndef HAVE_NOT_ESD_COPY if (fName.IsNull()) { // this is the first event, create the file name -- 2.39.3