We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As for any product, I think code profiling should be put in place.
I've done some researches and profiling node programs is not so easy 😕
Here are a few solutions I found:
node --prof script
Maybe the basic v8 profiling option is enough, but we need to find something to interpret it.
Otherwise, keep in mind that the idea is to have automatic profiling: no modification of the code!
The text was updated successfully, but these errors were encountered:
Implementing #41 would fix this issue for the editor module at least (the most important one): browsers contain profiling tools.
Sorry, something went wrong.
No branches or pull requests
As for any product, I think code profiling should be put in place.
I've done some researches and profiling node programs is not so easy 😕
Here are a few solutions I found:
node --prof script
. It produces a log file that can be inspected with some tools, but there are some issues with thoseMaybe the basic v8 profiling option is enough, but we need to find something to interpret it.
Otherwise, keep in mind that the idea is to have automatic profiling: no modification of the code!
The text was updated successfully, but these errors were encountered: