heroku-buildpack-jemalloc
delayed
Our great sponsors
| heroku-buildpack-jemalloc | delayed | |
|---|---|---|
| 3 | 3 | |
| 238 | 148 | |
| - | 2.0% | |
| 2.5 | 4.9 | |
| 6 months ago | 7 days ago | |
| Shell | Ruby | |
| BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
heroku-buildpack-jemalloc
-
Delayed Job vs. Sidekiq: Which Is Better?
Using jemalloc instead of regular malloc helps too. The exact way to do this depends on the platform you use, but it is pretty simple on Heroku. Just set heroku-buildpack-jemalloc as the first buildpack (ahead of the heroku/ruby buildpack).
I've recently discovered jemalloc, specifically when used with Heroku.
"Using jemalloc instead of regular malloc helps too. The exact way to do this depends on the platform you use, but it is pretty simple on Heroku. Just set heroku-buildpack-jemalloc as the first buildpack (ahead of the heroku/ruby buildpack)."
FYI, remember to set JEMALLOC_ENABLED=true in your env to actually turn it on.
https://github.com/gaffneyc/heroku-buildpack-jemalloc
-
Digital Ocean App Platform vs Heroku
Like I mentioned earlier, Digital Ocean App Platform uses the same buildpacks as Heroku to deploy your apps. This means that most apps that can be deployed on Heroku should also be deployed on Digital Ocean. There is one big caveat, though; you can't select which buildpack(s) to use. This means you have to rely on Digital Ocean to pick the right ones for your project. It also gives you a bit less flexibility in how your app runs. For instance, I recently configured our app at work to run using jemalloc, a malloc alternative that often has better performance for Ruby apps. We did that via a buildpack heroku-buildpack-jemalloc, which allowed us to switch to jemalloc without any app changes. Customizations to the build environment like this don't seem possible given the Digital Ocean App Platform's current offerings.
delayed
-
Introducing GoodJob Bulk and Batch
To be fair, I think GoodJob is the third youngest Active Job backend (released in 2020). The younger ones are Skiplock and betterment/delayed.
-
Delayed Job vs. Sidekiq: Which Is Better?
One big difference if you're changing forks is to take note of "at least once delivery": https://github.com/betterment/delayed#at-least-once-delivery
If you're not aware of that, simply switching repos may cause some surprises.
What are some alternatives?
Delayed::Job - Database based asynchronous priority queue system -- Extracted from Shopify
sidekiq-failures - Keep track of Sidekiq failed jobs
subdir-heroku-buildpack - Allows to use subdirectory configured via environment variable as a project root
good_job - Multithreaded, Postgres-based, Active Job backend for Ruby on Rails.
create-react-app-buildpack - ⚛️ Heroku Buildpack for create-react-app: static hosting for React.js web apps
sidekiq-statistic - See statistic about your workers
inst-jobs - Instructure-maintained fork of delayed_job
heroku-integrated-firefox-geckodriver - Buildpack enables your client code to access Firefox along with Geckodriver in a Heroku slug.
dotnetcore-buildpack - Heroku .NET Core Buildpack
RocketJob - Ruby's missing background and batch processing system