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.
  1. Raw TTreeCache: For the first cluster of TTree, read in all branches by default.
  2. Align learning periods in CMSSW to cluster boundaries.
  3. Don't reset learning in multicore mode for every event skip.
  4. 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.
  5. Ability to manually set the flush interval for RECO/AOD tiers. Will help mitigate the fast merge issues for these files.
  6. Repeat all improvements for FWLite.
  7. Double-buffering in TTreeCache (under development by CERN).
  8. Use TTreeCache-based I/O in fast merge.
  9. Fix statistics for native ROOT plugins.
  10. Fix fast merge of files with different flush intervals.
  11. Upstream raw TTreeCache into ROOT: Align training period length to cluster boundaries. For the first cluster of TTreeCache usage, read in all branches.
  12. TAdaptiveTreeCache: keep usage statistics from TBasket, and update the list of branches once every cluster transition.
Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2011-02-09 - BrianBockelman
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback