-
Notifications
You must be signed in to change notification settings - Fork 191
HTML-Heatmap-Generation in futhark profile
#2340
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
Conversation
Separate event summarisation from `tabulateEvents`
|
Problems I'm currently thinking about:
|
Ideally, in case of failure no output is produced. I think it is reasonable to produce all results in memory and only write them to disk at the end.
Parse all profiling data. I do not think there is reason to parse Futhark source at all. For highlighting, all you need is the source spans, which refer to byte offsets within the file.
Yes, and I do not think this will take up much memory. Futhark programs are small. |
|
Commit d098fc3 introduces a failure condition where an I/O-Error might abort the writing of the HTML-Files. |
|
That's reasonable. You build all the files up front and then write them at the end, so I/O errors outside of our control is the only thing that can go wrong. |
|
This is an example site generated by It does not have any information beyond the color embeddings right now. What I'm currently considering:
I opened the page locally in |
|
I can't figure out what's wrong with the I also have neither a windows nor a mac machine to reproduce and debug :( |
|
I fixed some cosmetic things and unified the CSS files. Remember to also update the CHANGELOG with a mention, including whatever name you wish to be credited under. |
|
Right now, this LocVolCalib.json (with no tricky relative paths) fail to be processed with |
|
Other (very simple) JSON files work, so I'm not quite sure what is going wrong. |
|
Oh yes, I already fixed it locally, sorry. It's related to the change I'm making because of the paths issue. I'm currently waiting for |
This is fixed from b3b373c onwards :) (works on my machine) |
|
Works on mine as well. This actually looks pretty promising. It takes some work to understand the results for complicated programs, but that is inherent to the problem - it is quite difficult to relate source ranges to cost centres for such an aggressively optimising compiler, but the foundation here is strong (and doing much better will require compiler engineering). |
Also adapt my old entry, I wasn't aware of the 80 character limit.
|
Thank you very much for you sustained assistance and help! I am done for today :] |
|
When CI works, I am liable to just merge this and start getting some experience with it. |
|
🥳 There are still a lot of queued checks from this branch, you might want to cancel them. E.g. right now the check for 9eab85d is running the |

closes #2339