Improved speed of hex parsing in more places #227
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Xyene
approved these changes
Jun 24, 2022
lamoreauxaj
force-pushed
the
use_fast_hex
branch
2 times, most recently
from
7a59d9d
to
b4532b1
Compare
lamoreauxaj
force-pushed
the
use_fast_hex
branch
2 times, most recently
from
d578b37
to
4dec2c3
Compare
…f maps with int64_of_hex_string. This addresses issue janestreet#93. Although janestreet#150 implemented fast hex string parsing, when I was magic-tracing magic-trace, I noticed unexpected lengthy calls to `Scanf` and related functions. This occurs because of calling `Int.Hex.of_string offset` within `parse_symbol_and_offset`. And this tends to take around 200-250 ns. Since this occurs about once per line in the `perf.data` file, the trace I ran this on executed this around 1.8 million times which should save a few hundred ms (out of total time of a few seconds). On traces after and before this change (respectively) of 3 decodes (which contain 3 executions of `parse_symbol_and_offset`) of a perf line containing an entry of the callstack sampled. The former is just below 2 us and the latter is around 2.6 us. However it is clear that most of the remaining time is now spent on evaluating regex in the former. In regards to implementation, I extracted these functions out to a `Util` module and used them when possible else where in magic-trace (although only the offset calculation is expensive because it is called a lot, but it seems reasonable to use them if possible). I used first class modules to abstract around `Int` and `Int64`. Signed-off-by: Aaron Lamoreaux <alamoreaux@janestreet.com>
lamoreauxaj
force-pushed
the
use_fast_hex
branch
from
4dec2c3
to
df0029f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This addresses issue #93. Although #150 implemented fast hex string parsing, when I was magic-tracing magic-trace, I noticed this in the trace:
This section of the trace entirely occurs because of calling
Int.Hex.of_string offsetwithinparse_symbol_and_offset. And this tends to take around 200-250 ns. Since this occurs about once per line in theperf.datafile, the trace I ran this on executed this around 1.8 million times which should save a few hundred ms (out of total time of a few seconds).Here are the traces after and before this change (respectively) zoomed in on 3 decodes (which shows 3 executions of
parse_symbol_and_offset) of a perf line containing an entry of the callstack sampled. The former is just below 2 us and the latter is around 2.6 us. However it is clear that most of the remaining time is now spent on evaluating regex in the former.In regards to implementation, I extracted these functions out to a
Utilmodule and used them when possible else where in magic-trace (although only the offset calculation is expensive because it is called a lot, but it seems reasonable to use them if possible). I used first class modules to abstract aroundIntandInt64.