Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-31905

in 3.6, __wt_update_obsolete_check, uses significant cpu

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.0-rc3
    • Component/s: WiredTiger
    • Labels:
      None
    • ALL
    • Hide

      This regularly occurs after a few minutes of running the ycsb benchmark. Happens on both x86 and power

      Show
      This regularly occurs after a few minutes of running the ycsb benchmark. Happens on both x86 and power

      the calls to __wt_update_obsolete_check from __col_instantiate and __row_instantiate were not in 3.4. between 3.4 and 3.6-r2 these calls were added and, as a result, __wt_update_obsolete_check cpu usage builds to over 20% of system

        1. ba357b7.diff
          0.9 kB
          Keith Bostic
        2. diag_log_3_6rc3.tar.gz
          7.02 MB
          Jim Van Fleet
        3. diag_log_3,4.tar.gz
          137 kB
          Jim Van Fleet
        4. jira.tar
          20 kB
          Jim Van Fleet

            Assignee:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Reporter:
            jvf Jim Van Fleet
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: