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
Hashing into UnresolvedReferences remains the slower part of the pipeline. Are there any other improvements can be made before storing the hash value inline?
I think the answer is yes, but I'm not quite sure how yet!
We should certainly be able to reduce hashing, but I don't know the internals of the hashmap we're using well enough to say best way to do it. We may not even need to store the whole hash, maybe just the top 7 bits of it (if it's a SwissTable-style hashmap).
From oxc-project/oxc#4169 (comment):
I think the answer is yes, but I'm not quite sure how yet!
We should certainly be able to reduce hashing, but I don't know the internals of the hashmap we're using well enough to say best way to do it. We may not even need to store the whole hash, maybe just the top 7 bits of it (if it's a SwissTable-style hashmap).
@Boshen Please remind me what software you are using to generate the perf measures shown in oxc-project/oxc#4169 (comment)?
The text was updated successfully, but these errors were encountered: