-
Notifications
You must be signed in to change notification settings - Fork 37
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
Get V8 Heap Usage #20
Comments
Thank you for your proposal. I think it's better to introduce built-in |
Well it would seem like v8 / the javascript world disagrees. Right now you can check memory in both node and chrome but both of those use this isolate heap memory stuff. While I agree that not adding a method to expose the V8 heap usage keeps v8eval simple, it does leave what I would argue an important, powerful feature (that already exists in v8) out. I think if your concern is keeping v8eval simple for new users there are better ways to do that. For instance we can put this function in a different file called At the end of the day if the goal of v8eval is just to provide a simple interface to v8 and nothing else that might be a reason to leave off heap memory usage. But I do not think that waiting for a v8 or an ecmascript |
I think it's not so difficult to implement |
I have released v8eval 0.2.6 that introduces |
If you are running long running v8 applications and are giving them lots of memory, it is often very useful to be able to inspect how much memory / heap each v8 isolate is using.
I propose that we add a simple method to
v8.go
on the v8 struct and the V8 interface that gives you back a struct where the attributes are uint64 values representing information about the isolates heap usage.Will send a pr with my proposal shortly.
The text was updated successfully, but these errors were encountered: