I used to use @profview (defiend in VSCodeServer) in vscode to analyze the cpu time of functions, which provide sth like this [image] The time costs are very clear. But now I get different result like the following using the same macro @profview [image] where has no information about time. T…

You can’t, at least not easily. In my experience the times reported by @profview were wildly inaccurate and mostly useless; in general, they are proportional to the sample count also shown in the new UI, so there shouldn’t be less info here (just less pretending to give you accurate timings).

Thanks, it seems I should get used to the new one.

If you really want the table though you can always profile manually

Not only you. The old way is a kind of ‘matlab’ style(what i hate…), but very easy to see although as pfitzseb said it’s inaccurate. I guess the inaccuracy is most big problem, and we should lean that ‘flame graph’ or anything…

I did a little research and here’s what I found. The “old way” was just generating a .cpuprofile file and opening it with vscode’s built-in .cpuprofile viewer, vscode-js-profile-visualizer , originally designed for js profiling. This is still possible to do manually by using ChromeProfileFormat.jl to…

@pfitzseb might have something to say about ProfileCanvas not being “actively developed” :wink: I seem to recall quite a bit of activity a few months back

You’re right, sorry. @pfitzeb has indeed been doing great work on this package, indeed he’s carried it solo up till now. It’s a good package to have, and it looks great! But he is after all just one person who by his own admission doesn’t have time to work on this feature. There is an issue open for…

As always, things like these are a matter of prioritization – we haven’t had many people telling us they’re missing the old UI, for example (roughly four, including this thread, if I remember correctly). Also note that the switch to our own UI did fix a actual issues with the previous solution, I d…

What happend to @profview

Tooling VS Code

jeffreyesun September 7, 2022, 9:35pm 5

I strongly prefer the old way. Why would you just remove a feature? It would also display the self and total times above each function. I know it wasn’t super accurate but it was extremely useful to me.

Topic		Replies	Views
Alternatives to flame graphs for profiler Profiling vscode , profiling	6	1103	November 20, 2023
Is VSCode `@profview` broken on 1.11? General Usage vscode , profiling	4	563	October 26, 2024
[ANN] Julia for VS Code v1.6 VS Code	9	1131	March 18, 2022
[ANN] ProfileSVG v0.2.0 Package Announcements profiling	5	1264	December 11, 2020
Profile results contains no samples from my code General Usage profile	2	137	May 6, 2025

What happend to @profview

Related topics