# Understanding mini-profiler output \`Executing action: show\`

**URL:** https://meta.discourse.org/t/understanding-mini-profiler-output-executing-action-show/40055
**Category:** Development
**Tags:** mini-profiler
**Created:** [February 23, 2016, 9:31pm UTC](https://meta.discourse.org/t/understanding-mini-profiler-output-executing-action-show/40055 "2016-02-23T21:31:30Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)
#### Post date: [February 23, 2016, 9:31pm UTC](https://meta.discourse.org/t/understanding-mini-profiler-output-executing-action-show/40055/1 "2016-02-23T21:31:30Z")

</div>

In between SQL statements I’m seeing `Executing action: show — XX.XX ms`

What exactly does do the `Executing action: show` times mean?

In a MySQL client you might see two times a “duration” (execution time) “fetch” (how long the data took to transfer over the wire).

The “show” time doesn’t seem to match “duration” or “fetch” in MySQL terms.

Sometimes “show” is many times larger than the sum of the previous queries so it would be good to understand what exactly is being done here.

Thanks!

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [February 23, 2016, 9:35pm UTC](https://meta.discourse.org/t/understanding-mini-profiler-output-executing-action-show/40055/2 "2016-02-23T21:35:16Z")

</div>

Do ?pp=flamegraph to get a full breakdown

Usually time outside of SQL is in Active Record and ranges from 30% on fast machines to 70% on slow machines for something like the topic page, depending on a pile of factors

---

<div class="post-metadata">

### Author: ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)
#### Post date: [February 23, 2016, 9:47pm UTC](https://meta.discourse.org/t/understanding-mini-profiler-output-executing-action-show/40055/3 "2016-02-23T21:47:50Z")

</div>

Adding `?pp=flamegraph` is “interesting”, not sure how this helps me understand a specific “show” that has already occurred.

If I spot a long “show” is there a way to see a flame graph of that specific one?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [February 23, 2016, 10:46pm UTC](https://meta.discourse.org/t/understanding-mini-profiler-output-executing-action-show/40055/4 "2016-02-23T22:46:46Z")

</div>

I can’t build a time machine 🙂 but if you repeat the same GET request with ?pp=flamegraph it will drill into what happens, in general performance is close enough for repeated requests.

If you get an outlier not much you can do.
