# Does stub\_status itself cause performance issues?

**URL:** <https://www.ruby-forum.com/t/does-stub-status-itself-cause-performance-issues/244088>\
**Category:** NGINX\
**Created:** [February 18, 2016, 3:34pm UTC](https://www.ruby-forum.com/t/does-stub-status-itself-cause-performance-issues/244088 "2016-02-18T15:34:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rafa\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/958977/32.png) [@Rafa\_F](https://www.ruby-forum.com/u/Rafa_F)\
**Post date:** [February 18, 2016, 3:34pm UTC](https://www.ruby-forum.com/t/does-stub-status-itself-cause-performance-issues/244088/1 "2016-02-18T15:34:31Z")

</div>

Hello,

I searched everywhere but found nothing. Is there an overhead of setting  
stub\_status page and activate it all the time? Using Apache’s  
ExtendedStatus  
for example has an impact on performance and recommended to be used only  
for  
debugging purposes, not all the time. What about stub\_status?

Posted at Nginx Forum:

> **[Does stub\_status itself cause performance issues?](https://forum.nginx.org/read.php?2,264592,264592#msg-264592)**
>
> Hello, I searched everywhere but found nothing. Is there an overhead of setting stub\_status page and activate it all the time? Using Apache's ExtendedStatus for example has an impact on performance and recommended to be used only for debugging...

---

<div class="post-metadata">

**Author:** ![raiblue](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/c5a1d2/32.png) [@raiblue](https://www.ruby-forum.com/u/raiblue)\
**Post date:** [March 10, 2016, 4:12am UTC](https://www.ruby-forum.com/t/does-stub-status-itself-cause-performance-issues/244088/2 "2016-03-10T04:12:52Z")

</div>

I did some performance tests and it seemed to me as-if the status stub  
caused a bit of a performance hit but nothing really concerning. However  
for the status stub doesn’t really give a lot of useful information IMO  
because its just supposed to be a placeholder for an nginx+ status page-  
I’m going the route of having a log tailer extract metrics.
