Move table resizing out of core mapping routine

Its placement there was not thread-safe and the mutex protecting the resize was killing performance in some applications.

Basic content checks passed!

Branch-at: 6423764e79ef0fffbf50c04422f11b42738c55f5
Acked-by: @kwrobot

@buildbot test

Your merge request has been queued for testing. You may view the test results on CDash or Buildbot.

Branch-at: 6423764e79ef0fffbf50c04422f11b42738c55f5

Added 1 commit:

• e61a328e - Move table resizing out of core mapping routine

Basic content checks passed!

Changes since last check: compare

Branch-at: e61a328e
Acked-by: @kwrobot

@buildbot test

Your merge request has been queued for testing. You may view the test results on CDash or Buildbot.

Branch-at: e61a328e

@utkarsh.ayachit @seanm @dgobbi

I'm not sure what the one Windows failure is about.

Sean and David, would you mind testing your applications against this branch and report any problems? Thanks.

Tested with my app and the performance is back to normal. Many thanks!

+1 Tested with tables built with Build() and with SetTable(), it worked with both (I used exactly the same test that crashed before you put in the mutex). Didn't see any problems with the code.

Thanks for testing so fast, Sean and David. I'm glad it's working for both of you.

Do: merge

Branch successfully merged and pushed!

Status changed to merged

mentioned in commit dbea2d5e