# \[ANN\] ProfileSVG v0.2.0

**URL:** <https://discourse.julialang.org/t/ann-profilesvg-v0-2-0/51657>\
**Category:** Package Announcements\
**Tags:** profiling\
**Created:** [December 11, 2020, 10:19am UTC](https://discourse.julialang.org/t/ann-profilesvg-v0-2-0/51657 "2020-12-11T10:19:33Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kimikage](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kimikage/32/14534_2.png) [@kimikage](https://discourse.julialang.org/u/kimikage)\
**Post date:** [December 11, 2020, 10:19am UTC](https://discourse.julialang.org/t/ann-profilesvg-v0-2-0/51657/1 "2020-12-11T10:19:33Z")

</div>

Dear all,

I am pleased to announce the release of [ProfileSVG v0.2.0](https://github.com/kimikage/ProfileSVG.jl/releases/tag/v0.2.0).

At JuliaCon 2020, held after the release of [ProfileSVG v0.1.3](https://discourse.julialang.org/t/ann-profilesvg-v0-1-3/38943), there were talks on VS Code, Pluto.jl etc., which had a significant impact on the Julia development environment.  
I do not have a clear answer as to the role of ProfileSVG in these revolutionary changes, but I do believe in the importance of “diversity”. 😄

One of the important changes is that ProfileSVG now supports HTML display. It is just the original SVG enclosed in HTML tags, and in many environments there is little or no change. However, this means that you can now use the interactive feature within Pluto.jl.

 ![pluto](https://global.discourse-cdn.com/julialang/original/3X/3/9/39d84cc48fa2e5caf67f6c0bd2bef2150b3aa816.png)

Also, the default color scheme has been changed. You can [customize the color scheme](https://kimikage.github.io/ProfileSVG.jl/v0.2/coloration-schemes/). In addition, support for several [other options](https://kimikage.github.io/ProfileSVG.jl/v0.2/other-options/) has been added.

In the next v0.3 series, I plan to improve the interactive UI.

Although the development speed is slow, I am looking forward to your feedback!

---

<div class="post-metadata">

**Author:** ![juliohm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juliohm/32/215266_2.png) [@juliohm](https://discourse.julialang.org/u/juliohm)\
**Post date:** [December 11, 2020, 11:29am UTC](https://discourse.julialang.org/t/ann-profilesvg-v0-2-0/51657/2 "2020-12-11T11:29:07Z")

</div>

Thanks for the contribution! It would be nice to embed a profile viewer in VS Code! Either ProfileSVG.jl or ProfileView.jl. Can you elaborate on the differences between the two packages?

---

<div class="post-metadata">

**Author:** ![kimikage](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kimikage/32/14534_2.png) [@kimikage](https://discourse.julialang.org/u/kimikage)\
**Post date:** [December 11, 2020, 11:50am UTC](https://discourse.julialang.org/t/ann-profilesvg-v0-2-0/51657/3 "2020-12-11T11:50:31Z")

</div>

See also [Julia VS Code extension version v0.17 released](https://discourse.julialang.org/t/julia-vs-code-extension-version-v0-17-released/42865)  
This is the reason why I mentioned the VS Code. 😄

The difference between ProfileSVG.jl and ProfileView.jl is that the former outputs SVG “image”, while the latter launches a stand-alone GTK-based widget.

The feature allows ProfileSVG to display profiling results in the Plot Pane of VS Code, just like any other plotting package.

 ![vscode_profiling](https://global.discourse-cdn.com/julialang/original/3X/6/9/69fe4c1ecc045951a9a956376934c50b652377ad.png)

---

<div class="post-metadata">

**Author:** ![juliohm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juliohm/32/215266_2.png) [@juliohm](https://discourse.julialang.org/u/juliohm)\
**Post date:** [December 11, 2020, 11:54am UTC](https://discourse.julialang.org/t/ann-profilesvg-v0-2-0/51657/4 "2020-12-11T11:54:39Z")

</div>

I thought that Juno had integration with ProfileView.jl at some point without a Gtk window, but I may be confusing something. What I meant is that users could just select a script and click a button in VS Code to profile. No need to write the profile calls and to warm up the compiler. These details should be hidden from the end user.

---

<div class="post-metadata">

**Author:** ![kimikage](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kimikage/32/14534_2.png) [@kimikage](https://discourse.julialang.org/u/kimikage)\
**Post date:** [December 11, 2020, 12:04pm UTC](https://discourse.julialang.org/t/ann-profilesvg-v0-2-0/51657/5 "2020-12-11T12:04:22Z")

</div>

Yes, Juno had (has) its own profile-viewing feature.  
[http://docs.junolab.org/stable/man/juno\_frontend/#Profiler-1](http://docs.junolab.org/stable/man/juno_frontend/#Profiler-1)

---

<div class="post-metadata">

**Author:** ![martincornejo](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/martincornejo/32/13436_2.png) [@martincornejo](https://discourse.julialang.org/u/martincornejo)\
**Post date:** [December 11, 2020, 3:12pm UTC](https://discourse.julialang.org/t/ann-profilesvg-v0-2-0/51657/6 "2020-12-11T15:12:19Z")

</div>

> [@juliohm](#):
>
> It would be nice to embed a profile viewer in VS Code

> [@kimikage](#):
>
> Juno had (has) its own profile-viewing feature.

Just like Juno, VS Code has also its own profile-viewing feature. Without any additional package you can use the `@profview` macro and by adding the VS Code [profile visualizer](https://github.com/microsoft/vscode-js-profile-visualizer) you can generate flame graphs.