Heroku recommends keeping it between .5 and 1 for non-performance dynos, so
you should be fine there.

I highly recommend the New Relic addon for Heroku - should be free for your
current set up.  Makes it very easy to see both web and background job
request times, dyno memory usage, etc. I also love Airbrake for error
tracking.

On Thu, Sep 27, 2018 at 11:30 AM Chris McCann <[email protected]> wrote:

> All,
>
> I currently run Airnoise.io on Heroku with one web and two worker dynos.
>
> When I look at the metrics for the web dyno I often wonder what values of
> Response Time, Throughput, and Dyno Load would indicate the need for an
> additional web dyno.
>
> Occasional spikes of Dyno Load to 1.0 make me wonder if the web dyno is
> getting saturated with requests, but I don't really see any way to tell if
> requests are being dropped.
>
> If anyone has some experience in using the Heroku metrics to help guide
> their scaling, or if tools like New Relic offer better, more actionable
> data, I'd love to hear how you use those tools to manage your Heroku
> infrastructure.
>
> Cheers,
>
> Chris
>
> --
> --
> SD Ruby mailing list
> [email protected]
> http://groups.google.com/group/sdruby
> ---
> You received this message because you are subscribed to the Google Groups
> "SD Ruby" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
--- 
You received this message because you are subscribed to the Google Groups "SD 
Ruby" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to