Skip to content
Snippets Groups Projects
Commit e23967f7 authored by Timo Koch's avatar Timo Koch
Browse files

[bugfix][gridgeometry] Always construct bboxtree and element map

A thread-safe implementation with double-checked lock needs atomic load/store
operations to update the pointer to be thread-safe. Alternatively, a lock
has to be acquired every time when the function is called. Both implementations
impair the scalability of the multihreaded assembly (in the case of tpfa, or
any simulation that uses element maps or bounding box tree on an element level).

This changes the beahviour to always build the tree and the element map. This
usually occurs little runtime overhead in cases where the features are unused.
It is the most performant version as soon as one of the features is used.
There is however some memory overhead in the order of one or more ints per
element (seeds) and a bounding box hierarchy.
parent 0528733e
No related branches found
No related tags found
1 merge request!3095[bugfix][gridgeometry] Always construct bboxtree and element map
Pipeline #16029 passed
Pipeline: dumux-lecture

#16034

    Pipeline: dumux

    #16033

      Pipeline: dumux

      #16032

        +2
        Loading
        0% Loading or .
        You are about to add 0 people to the discussion. Proceed with caution.
        Finish editing this message first!
        Please register or to comment