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

Create the breakdown profiling of slang #4209

Closed
kaizhangNV opened this issue May 22, 2024 · 2 comments
Closed

Create the breakdown profiling of slang #4209

kaizhangNV opened this issue May 22, 2024 · 2 comments
Assignees
Labels
goal:client support Needed to support a slang use case

Comments

@kaizhangNV
Copy link
Contributor

Currently we only profile the total compile time and downstream compile time of slang. But we really need a way to have a breakdown the front-end, link, back-end compile time.

Also, we noticed that there is performance regression on the latest slang version comparing to v0.24.x, so we need to back-port the profiler to the older version such that we can have a reliable comparison.

@kaizhangNV kaizhangNV self-assigned this May 22, 2024
@jkwak-work
Copy link
Collaborator

There are two command-line arguments for slangc.exe: -report-downstream-time and -report-perf-benchmark.
It sounds like this task will be to improve -report-perf-benchmark, is it?
Or do we need a new compiler option for this task?

@jkwak-work
Copy link
Collaborator

jkwak-work commented May 22, 2024

Just FYI, here is how it looks like when I used -report-perf-benchmar,

$ build/Release/bin/slangc.exe -report-perf-benchmark tests/glsl-intrinsic/intrinsic-basic.slang -allow-glsl
(0): note 103: compiler performance benchmark:
loadStdLib:     1       198
checkAllTranslationUnits:       2       1039
generateIRForTranslationUnit:   2       155
performMandatoryEarlyInlining:  7       9

Type Dictionary Size: 2575

@swoods-nv swoods-nv added the goal:client support Needed to support a slang use case label May 23, 2024
@csyonghe csyonghe closed this as completed Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
goal:client support Needed to support a slang use case
Projects
None yet
Development

No branches or pull requests

4 participants