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

Poor performance when handling huge isolate-v8.log file #50

Open
SukkaW opened this issue Jul 23, 2024 · 3 comments
Open

Poor performance when handling huge isolate-v8.log file #50

SukkaW opened this issue Jul 23, 2024 · 3 comments

Comments

@SukkaW
Copy link

SukkaW commented Jul 23, 2024

For some reason, with the dexnode I end up with an isolate-v8.log file at the size of 232 MiB.

$ ls -lah isolate-0x150008000-91458-v8.log
-rw-r--r--@ 1 sukka  staff   232M Jul 23 18:24 isolate-0x150008000-91458-v8.log

And I am stuck at this for 8 minutes, yet it is still loading:

image image
@SukkaW
Copy link
Author

SukkaW commented Sep 16, 2024

@rbuckton Hello?

@rbuckton
Copy link
Member

NodeJS/v8 will continue writing to the isolate log until the process exits, which can result in very large files and can take a long time to process. Unfortunately, I do not have a solution for this at the moment, so your best option is to try to isolate the scenario you are investigating as much as possible so as to reduce the size of the log file.

@SukkaW
Copy link
Author

SukkaW commented Sep 16, 2024

to reduce the size of the log file

I am profiling my script, the process only runs for 10 seconds, yet it produces 200 MiB of v8 log.

Does it have something to do with the Node.js module register? I am using dexnode -r @swc-node/register to profile my script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants