# Jenkins on small environment, taking too much RAM, too much processes

**URL:** <https://community.jenkins.io/t/jenkins-on-small-environment-taking-too-much-ram-too-much-processes/3975>\
**Category:** Ask a question\
**Tags:** question\
**Created:** [September 27, 2022, 11:24am UTC](https://community.jenkins.io/t/jenkins-on-small-environment-taking-too-much-ram-too-much-processes/3975 "2022-09-27T11:24:38Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\
**Post date:** [September 30, 2022, 4:40pm UTC](https://community.jenkins.io/t/jenkins-on-small-environment-taking-too-much-ram-too-much-processes/3975/4 "2022-09-30T16:40:52Z")

</div>

Are you confident that you’ve made the correct edits to the Jenkins service unit?

On my Ubuntu 22.04 machine, I installed Jenkins 2.361.1 using the Ubuntu installation instructions. I configured Jenkins and confirmed that `top` showed that it was using 2 GB of heap. I edited the systemctl override with `systemctl edit jenkins` and inserted the following changes

```auto
[Unit]
Description=Jenkins ubuntu-22-a

[Service]
# Arguments for the Jenkins JVM
Environment="JAVA_OPTS=-Xmx512M -Djava.awt.headless=true"

```

I used `systemctl daemon-reload` to assure that the new configuration was read, then used `systemctl restart jenkins` to restart the Jenkins controller.

After the restart, `top` reported that Jenkins was using less than 512M.

---

_[View the full topic](https://community.jenkins.io/t/jenkins-on-small-environment-taking-too-much-ram-too-much-processes/3975)._