You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that BingSNR (when I run it locally on Windows-x64) emits 44k jump stubs (44k calls to allocJumpStubBlock) - it happens because the app itself is quite big and its working set is 7-10Gb (thus, we likely have multiple loaderheaps) running locally for a benchmark. Also I noticed that the process of emitting jump stubs is quite hot, e.g. here is a flamegraph for a randomly selected time frame after start: 50s - 60s:
Can we do anything with this? E.g. just like in #64148 to emit 64bit addresses to precode slots directly in methods
The text was updated successfully, but these errors were encountered:
I noticed that BingSNR (when I run it locally on Windows-x64) emits 44k jump stubs (44k calls to
allocJumpStubBlock
) - it happens because the app itself is quite big and its working set is 7-10Gb (thus, we likely have multiple loaderheaps) running locally for a benchmark. Also I noticed that the process of emitting jump stubs is quite hot, e.g. here is a flamegraph for a randomly selected time frame after start: 50s - 60s:Can we do anything with this? E.g. just like in #64148 to emit 64bit addresses to precode slots directly in methods
The text was updated successfully, but these errors were encountered: