# How to zoom in on profiler view

**URL:** <https://discourse.julialang.org/t/how-to-zoom-in-on-profiler-view/31190>\
**Category:** Juno\
**Created:** [November 17, 2019, 7:53pm UTC](https://discourse.julialang.org/t/how-to-zoom-in-on-profiler-view/31190 "2019-11-17T19:53:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![xzackli](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/xzackli/32/38301_2.png) [@xzackli](https://discourse.julialang.org/u/xzackli)\
**Post date:** [November 17, 2019, 7:53pm UTC](https://discourse.julialang.org/t/how-to-zoom-in-on-profiler-view/31190/1 "2019-11-17T19:53:43Z")

</div>

Is there a way to zoom in on output from `Juno.profiler()`? When I use the scroll wheel or the +/- buttons in the graphical interface, it appears to just pan the output.

---

<div class="post-metadata">

**Author:** ![LaurentPlagne](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/laurentplagne/32/10103_2.png) [@LaurentPlagne](https://discourse.julialang.org/u/LaurentPlagne)\
**Post date:** [November 17, 2019, 9:07pm UTC](https://discourse.julialang.org/t/how-to-zoom-in-on-profiler-view/31190/2 "2019-11-17T21:07:49Z")

</div>

I wonder if Juno.profiler() is mature enough at this point because, compared to ProfileView, you loose the coloring and especially the red color that helps a lot to spot type and allocation issues.  
In addition it is quite easy to zoom in ProfileView.

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [November 18, 2019, 11:32am UTC](https://discourse.julialang.org/t/how-to-zoom-in-on-profiler-view/31190/3 "2019-11-18T11:32:10Z")

</div>

What version of julia-client and ink are you running? I can zoom just fine on the latest versions, so you might be running into a bug that’s already fixed.

> [@LaurentPlagne](#):
>
> you loose the coloring and especially the red color that helps a lot to spot type and allocation issues.

Should be fairly easy to add those, but we only got a feature request asking for that 5 days ago:

> <https://github.com/JunoLab/Juno.jl/issues/428>
>
> Function calls resolved at runtime are a usual sign of type inference problems a…nd can incur significant performance costs. It would be nice if the flamegraph output of the profiler highlighted these calls somehow. For example, \`ProfileView\` highlights these calls in red.

---

<div class="post-metadata">

**Author:** ![LaurentPlagne](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/laurentplagne/32/10103_2.png) [@LaurentPlagne](https://discourse.julialang.org/u/LaurentPlagne)\
**Post date:** [November 18, 2019, 11:50am UTC](https://discourse.julialang.org/t/how-to-zoom-in-on-profiler-view/31190/4 "2019-11-18T11:50:24Z")

</div>

Hi, I am an enthusiast Juno’s user so I hope I did not offended you with my comment on the Juno.profiler() maturity.

This is probably very difficult and time consuming to achieve but a profile view based on the valgrind strategy (nested boxes) would be very useful for me.

 ![valgrind-map-graph-01](https://global.discourse-cdn.com/julialang/original/3X/0/c/0c82e16a2db24d057d03134e2783d4aae8cab1ec.png)