heroku-buildpack-jemalloc VS subdir-heroku-buildpack

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

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.

C:\Users\RaiqP\Desktop\Skiplagged\backend>git push heroku master Enumerating objects: 9488, done. Counting objects: 100% (9488/9488), done. Delta compression using up to 16 threads Compressing objects: 100% (6996/6996), done. Writing objects: 100% (9488/9488), 12.75 MiB | 690.00 KiB/s, done. Total 9488 (delta 2049), reused 9488 (delta 2049), pack-reused 0 remote: Compressing source files... done. remote: Building source: remote: remote: -----> Building on the Heroku-20 stack remote: -----> Using buildpacks: remote: 1. https://github.com/timanovsky/subdir-heroku-buildpack.git remote: 2. heroku/nodejs remote: -----> Subdir buildpack app detected remote: PROJECT_PATH is undefined remote: ! Push rejected, failed to compile Subdir buildpack app. remote: remote: ! Push failed remote: ! remote: ! ## Warning - The same version of this code has already been built: 782398522d1daa7a09f5296d7e03bcf9f0604244 remote: ! remote: ! We have detected that you have triggered a build from source code with version 782398522d1daa7a09f5296d7e03bcf9f0604244 remote: ! at least twice. One common cause of this behavior is attempting to deploy code from a different branch. remote: ! remote: ! If you are developing on a branch and deploying via git you must run: remote: ! remote: ! git push heroku :main remote: ! remote: ! This article goes into details on the behavior: remote: ! https://devcenter.heroku.com/articles/duplicate-build-version remote: remote: Verifying deploy... remote: remote: ! Push rejected to heroku-skiplagged-final. remote: To https://git.heroku.com/heroku-skiplagged-final.git ! [remote rejected] master -> master (pre-receive hook declined) error: failed to push some refs to 'https://git.heroku.com/heroku-skiplagged-final.git'

Enter this url to add buildpack https://github.com/timanovsky/subdir-heroku-buildpack.git and make sure this is at the top of the buildpack chain (drag the lines on the left to make it above any other buildpacks you have added.

https://github.com/timanovsky/subdir-heroku-buildpack

Under the Config Vars section, you will see the Buildpack section. Click on add Buildpack and enter https://github.com/timanovsky/subdir-heroku-buildpack.git as the URL. Save changes.