René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"more performant build of Geant4 by default","articleBody":"The default value of a few configuration parameters in Geant4 have values that are helpful for initial development of a Geant4 application but are unhelpful when attempting to scale up to larger production systems. I think, especially with the introduction of #83 enabling local custom G4 builds, we could update the configuration of G4 to be focused on performance _only_ and guide people to rebuild locally with different configuration if they need more information from the G4 side for debugging/development purposes.\r\n\r\nI use `cmake -LAH` to list all of the available `option`s and noticed a few that have some non-performant defaults.\r\n\r\nOption | Default | Description\r\n---|---|---\r\nCMAKE_BUILD_TYPE | RelWithDebInfo | type of build, this reduces the optimization and enables storing of the debug flags\r\nGEANT4_BUILD_VERBOSE_CODE | ON | include extra comments and checks during the simulation\r\nGEANT4_BUILD_STORE_TRAJECTORY | ON | build full trajectories during the simulation for visualization purposes\r\n\r\nI think the last option could be significantly contributing to simulation time since Geant4 is storing a particles full trajectory during its lifetime which could amount to many hundreds of steps that it needs to allocate and de-allocate on each track.\r\n\r\n### Context\r\nDiscovered while working on https://github.com/LDMX-Software/geant4/issues/13\r\n","author":{"url":"https://github.com/tomeichlersmith","@type":"Person","name":"tomeichlersmith"},"datePublished":"2024-02-07T19:28:57.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":12},"url":"https://github.com/92/dev-build-context/issues/92"}