1

The setup: Ruby 2.2.5 running on Heroku, sidekiq 4.1.1 for processing asynchronous jobs. MongoDB + mongoid on the backend, so no ActiveRecord.

We have been having memory issues on Heroku, so we increased the dyno size to a PX dyno, which increases the memory and CPU speed. Instead of seeing the job execution time (given to us by New Relic) stay the same or decrease, as expected, we found that it went up noticeably, over 2x in some cases. I can't imagine why this would be the case - how does more resources equal more time to execute the same work?

Improve this question
1
  • You really need to ask the Heroku guys. They've responded well to my trouble tickets in the past, and my project is quite small. Commented May 5, 2016 at 4:14
Related questions
6
(Heroku + Sidekiq) Is my understanding of how Connection Pooling works correct?
1
sidekiq-pro batches don't appear to release redis memory after batches complete
4
How to decide concurrency number in Sidekiq for CPU/RAM expensive jobs?
Load 5 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.