Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8329134

Reconsider TLAB zapping

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Fixed
    • P4
    • 23
    • 17, 21, 22, 23
    • hotspot
    • gc
    • b17

    Description

      We zap the entire TLAB on initial allocation (MemAllocator::mem_allocate_inside_tlab_slow), and then also rezap the object contents when object is allocated from the TLAB (ThreadLocalAllocBuffer::allocate). The second part seems excessive, given the TLAB is already fully zapped.

      There is also no way to disable this zapping, like you would in other places with the relevant Zap* flags.

      Fixing both these issues allows to improve fastdebug tests performance, e.g. in jcstress.

      Attachments

        Issue Links

          Activity

            People

              shade Aleksey Shipilev
              shade Aleksey Shipilev
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: