Since Jenkins runs on top of a Java VM, it will eat up available RAM at an alarming rate and is usually the biggest hog of usage along with being the most frequent out-of-memory (OOM) culprit I have had experience with. In even the lightest use cases, plan to allocate at least 1 GB of RAM to Jenkins workers or risk various failures at the most inopportune stages of your build pipelines. As a general rule, most Jenkins installation at this time will not have many problems with 2 GB of RAM allocated to them, but due to the price of RAM in VM instances, you can try to scale things back until you reach the acceptable levels of performance.

The last thing to also pay attention to is that the Jenkins image is also a bulky one relatively speaking, weighing in at about a hefty 800 MB, so keep in mind that moving this container is really not as easy nor fast as some other tooling that we have been using.