-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[wasm] Enable the log profiler #107434
[wasm] Enable the log profiler #107434
Conversation
55c005e
to
c10694a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jeromelaban what's the size of libmono-profiler-log.a
?
@pavelsavara interestingly, the dotnet.native.wasm seems to be smaller by 20 bytes with the log profiler included. |
adding |
Avoid "MSBUILD : error MSB1005: Specify a property and its value."
There is about 1kb size growth in the range for the default build. But I can't tell if this is the .wasm file or DLLs. There are other changes in the diff. @radekdoulik could you please advise ? |
* feat(wasm): Enable the log profiler * chore: Disable for wasi * chore: Add log profiler docs * chore: Adjust flush logs syntax * chore: Adjust defines, add conditionals, remove Module dependency * chore: Adjust buffer_unlock exclusion * chore: Adjust doc * chore: Add log profiler sample * chore: Add more sample logging * chore: Remove unused makefile target * chore: Remove icall, use jit interception to take heap sot * chore: Remove unused logs * chore: Remove unused dependency * Revert "chore: Remove unused dependency" This reverts commit 33221c4. * remove ENABLE_BROWSER_PROFILER from default build * Draft of WBT. * Miss-commit, there's no profiler.js in the sample. * Shift the responsibility of checking profile's size to the browser. * Test linking of all 3 types of loggers + running one of them. * link all 3 at the same time * fix [Fact] * Treat a list of loggers as one argument. Avoid "MSBUILD : error MSB1005: Specify a property and its value." * fix? --------- Co-authored-by: pavelsavara <pavel.savara@gmail.com> Co-authored-by: Ilona Tomkowicz <itomkowicz@microsoft.com> Co-authored-by: Ilona Tomkowicz <32700855+ilonatommy@users.noreply.github.com> Co-authored-by: Pavel Savara <pavelsavara@microsoft.com>
* feat(wasm): Enable the log profiler * chore: Disable for wasi * chore: Add log profiler docs * chore: Adjust flush logs syntax * chore: Adjust defines, add conditionals, remove Module dependency * chore: Adjust buffer_unlock exclusion * chore: Adjust doc * chore: Add log profiler sample * chore: Add more sample logging * chore: Remove unused makefile target * chore: Remove icall, use jit interception to take heap sot * chore: Remove unused logs * chore: Remove unused dependency * Revert "chore: Remove unused dependency" This reverts commit 33221c4. * remove ENABLE_BROWSER_PROFILER from default build * Draft of WBT. * Miss-commit, there's no profiler.js in the sample. * Shift the responsibility of checking profile's size to the browser. * Test linking of all 3 types of loggers + running one of them. * link all 3 at the same time * fix [Fact] * Treat a list of loggers as one argument. Avoid "MSBUILD : error MSB1005: Specify a property and its value." * fix? --------- Co-authored-by: pavelsavara <pavel.savara@gmail.com> Co-authored-by: Ilona Tomkowicz <itomkowicz@microsoft.com> Co-authored-by: Ilona Tomkowicz <32700855+ilonatommy@users.noreply.github.com> Co-authored-by: Pavel Savara <pavelsavara@microsoft.com>
This change adds the support for the log profiler discussed in #107312 for webassembly.
The inclusion follows the support for the browser and aot profilers.
Closes #107312