1. 18 Jun, 2021 1 commit
    • Vulkan: Free DynamicBuffer buffers after dip in allocation size · 24155b13
      Shahbaz Youssefi authored
      In a pattern like this:
      
      - allocate 100 bytes
      - allocate 200 bytes
      - allocate 50 bytes
      - allocate 100000000 bytes
      - allocate 100 bytes
      - allocate 200 bytes
      - allocate 50 bytes
      
      The DynamicBuffer class switches to making 100MB allocations even if
      that allocation was a one-off.  A small future allocation would then tie
      up 100MB in memory for future allocations.  Another 100MB is also left
      tied up in the free list.
      
      With this change, if an allocation is made that's less than a quarter of
      the DynamicBuffer's current allocation size, it's taken as a sign that
      the previous large allocation was a one-off and the size is moved back
      to the DynamicBuffer's original initial size.
      
      Bug: b/187757166
      Change-Id: I0c6f00eec7c81298f9dc41a41cc308510ce76623
      Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/2971004Reviewed-by: 's avatarCharlie Lao <cclao@google.com>
      Reviewed-by: 's avatarJamie Madill <jmadill@chromium.org>
      Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>
  2. 17 Jun, 2021 6 commits
  3. 16 Jun, 2021 19 commits
  4. 15 Jun, 2021 9 commits
  5. 14 Jun, 2021 5 commits