Skip to content
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

optimize memory usage #140

Open
nhooyr opened this Issue Mar 8, 2019 · 2 comments

Comments

Projects
None yet
3 participants
@nhooyr
Copy link
Collaborator

nhooyr commented Mar 8, 2019

See #136

@nhooyr nhooyr added the perf label Mar 8, 2019

@kylecarbs kylecarbs added the complex label Mar 8, 2019

@kylecarbs

This comment has been minimized.

Copy link
Member

kylecarbs commented Mar 8, 2019

This will require a significant amount of refactoring in the way we fork processes. Will likely require a custom binary packaging system.

@sr229

This comment has been minimized.

Copy link

sr229 commented Mar 18, 2019

a more likely patch as well is to tell V8 to go JITLess and use Ignition, which should tell the engine to no longer allocate a stack for compiling bytecode and instead use the interpreter. This approach has been seen to improve performance so I believe we can set this as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
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.