LHCb Core Software Meeting

Date and Location

10:30 - 11:11
CERN (2-R-030)


Ben Couturier, Gaylord Cherencey, Illya Shapoval, Marco Cattaneo, Marco Clemencic (minutes), Markus Frank, Stefan Lohn, Thomas Hartmann (Vidyo)


Gloria Corti



  • Gaylord's last week at CERN
  • LIM:
    • will test the drop of zlib (conflicting with the system version of libxml2)
    • preliminary tests of MacOSX 10.8 (Mounatin Lion) in September
    • removed multiprocessing from pytools (not needed)

Hot Topics

  • Marco Ca. boost::ordered_free saga:
    We introduced the use of ordered_malloc/ordered_free allocators in LHCb v35r1, to allow releasing unused memory from the Boost memory pools. This turned out to be a mistake because ordered_free is very slow and was adding an average of 4 seconds/event to the Brunel processing time. A new release has been made reverting the old behavior. We need the following patches:
    • In GaudiObjDesc DTD: add a flag that allows to turn on these allocators selectively (done), to allow a future fine grained tuning of their use
    • In SequencerTimer: add a timer to measure time spent between endEvent and beginEvent. Above increase in time was missed during initial tests because the destructors of the TES objects are called outside of the TopAlgs execution. (task #32735)
  • Marco Cl. Problem of slowness of the nightlies probably understood (thanks to Marco Ca. for the hint to the correlation): a new feature in LCGCMT 64 causes a lot of stress on AFS.
    • Work-around in GaudiPolicy to be used in all the slots.
    • Next LCGCMT will feature a fix.

Issues from last meeting

  • Investigate the memory explosion in FSR merging
    • Rob found a possible cause.
  • Fix the dependency of GaudiObjDesc on LHCbKernel Marco Cl.
    • Added a link library to GaudiObjDesc and moved the code from LHCbKernel.
    • Performance problem due to ordered_free discovered in Brunel: modified GaudiObjDesc to use the old allocators as default, but allow the switch to the ordered ones in individual classes.
  • Circulate a proposal for adding the license to Gaudi Marco Cl.
    • pending
  • Organize the tests for the use of Frontier in production.
    • pending

Round Table

Marco Cl.

  • Mistake in the configuration of the nightlies: using head of everything for Gaudi instead of only head of GaudiPolicy.
  • Received from Coverity instructions to fix the problem with the upgrade.
  • Working on CMake: the priority of the task have to be raised because of pending issues
    • automatic translation of requirements (not complete)
    • handling of "data packages" (issue shared with RPM-based packaging)
    • SetupProject integration (plus some details for the environment)
  • Will start some clean up of obsolete code in GaudiObjDesc.
  • How do we want to build the releases? mkproject does not use distcc and does not build packages in parallel, while the nightlies do it. Shall we change?
    Let's do it.


  • Problem with exceptions not being recognized (output of a test different between gcc43 and gcc46)


  • Still pushing to get gcc46 builds for Ganga and LHCbDirac. Prerequisite to change the default to gcc46.


  • Marco Cl.: Benedikt will have a new SLC6 that will share with us (via lhcbsoft account).
    Ben: Our own SLC6 is ready, just waiting for Joel.


  • Circulate a proposal for adding the license to Gaudi Marco Cl.
  • Organize the tests for the use of Frontier in production Marco Cl.
  • Upgrade Coverity installation Marco Cl.
  • Check if Frontier keeps connections open. Marco Cl.
  • Change the call to make in mkproject Ben
  • Fix the environment on lxplus when using cvmfs Ben

-- MarcoClemencic - 01-Aug-2012

Edit | Attach | Watch | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r4 - 2012-08-01 - MarcoClemencic
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LHCb 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