-
-
Notifications
You must be signed in to change notification settings - Fork 502
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
perf(ast): reduce AST memory usage #5601
Comments
There is a value to reducing memory usage. But is there a gain to reducing types to under 64 bytes? Some types are just inherently big, as they contain a lot of info (e.g. In my opinion, the fields which we should consider boxing are either:
e.g.:
I imagine that the majority of code that Oxc will run against will be plain JS (when bundling an application, the volume of library code in Also: We can expect |
I boxed a few attributes in the PR stack #5679, everything else looks fine. |
…asi` by `Boxing` it (#5679) (#5715) As discussed in #5601, there is little benefit to reducing type sizes for the sake of it. In this case, the `quasi` field in not in an `Option`, so putting it in a `Box` does not save data, only moves where that data is stored, and introduces pointer-indirection.
Structs / enums larget than 64 bytes should be reduced:
The text was updated successfully, but these errors were encountered: