Use relaxed semantics for variables related to obsolete time window

XMLWordPrintableJSON

    • Storage Engines, Storage Engines - Transactions
    • StorEng - Defined Pipeline
    • 3

      The __wt_heuristic_controls contains the following variables:

          /* Number of btrees processed in the current checkpoint. */
          wt_shared uint32_t obsolete_tw_btree_count;
      
          /* Maximum number of pages that can be processed per btree by checkpoint cleanup. */
          uint32_t checkpoint_cleanup_obsolete_tw_pages_dirty_max;
      
          /* Maximum number of pages that can be processed per btree by eviction. */
          uint32_t eviction_obsolete_tw_pages_dirty_max;
      
          /* Maximum number of btrees that can be processed per checkpoint. */
          uint32_t obsolete_tw_btree_max;
      

      This ticket should look into using __atomic_load and __atomic_store for those variables.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Etienne Petrel
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: