Difference: CmsRootIoIssues (2 vs. 3)

Revision 32011-02-09 - BrianBockelman

Line: 1 to 1
 
META TOPICPARENT name="CmsXrootdArchitecture"

Top Issues in ROOT and CMSSW I/O

These refer to pure I/O, and ignore the issues in the serialization/deserialization of CMS data structures.
Line: 7 to 7
 
  1. Don't reset learning in multicore mode for every event skip.
  2. Ability to add all branches to TTreeCache from config file. Note: with the exception of the high-latency case, there's almost no standard use case where reading the whole event doesn't make sense.
  3. Ability to manually set the flush interval for RECO/AOD tiers. Will help mitigate the fast merge issues for these files.
Added:
>
>
  1. Repeat all improvements for FWLite.
 
  1. Double-buffering in TTreeCache (under development by CERN).
  2. Use TTreeCache-based I/O in fast merge.
  3. Fix statistics for native ROOT plugins.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback