JamfPro Server Resourse Hungry

iVoidWarrantiez
New Contributor III

I built my JamfPro server on a CentOS 7 VM. It is not a repo or distribution point just the apache tomcat server and the mysql server. It uses a lot more RAM that I was expecting.

I started with 2gig and quickly noted it was using almost all of it. Took it to 4gig and again noted it was using almost all of it. Now I am running with 8gig but using 4.8 of the 8 gigs. I have the RAM 'to spare' so to speak on my VM host but I configured it this way trying to save resources.

I can note that is uses more ram as we use the webUI more and more. Almost as if it using it but not freeing it once done. Anybody else have any insight or knowledge one this matter? I would love to take it down to 2 but 4 is fine.

CPU usage is fine.

Thanks in advance.

*Side note, my master repo is running CentOS 7 as well (dedicated VM) but only 512meg of ram and running beautiful.

2 ACCEPTED SOLUTIONS

wmayhone
New Contributor III

Is everything running on the one server? 2GB isn't going to cut it, and depending on how often devices are communicating to Jamf Pro, and how many you add, 4GB probably won't be enough either. Have you opened a case with Jamf Support yet to get their recommendations?

View solution in original post

hdsreid
Contributor III

The more users you have using the console, enrolled, executing policies, etc, the more ram will be used. 8GB ram is considered the minimum for building home computers at this point, do not be surprised if an enterprise server is going to consume ram like it is going out of style.

Almost as if it using it but not freeing it once done

why would you want it to be freed? having it inactive but still retaining information will make the server run "faster" for users on the web console since it does not have to reload everything in to memory.

I would love to take it down to 2 but 4 is fine

again - why? are you short on memory in your virtual environment? if so, you'll need to expand that or get dedicated hardware for your JSS (or have it cloud hosted if you feel strongly about that). your usage is only going to go up, not down, as you add devices and additional jamf pro users into your environment.

View solution in original post

5 REPLIES 5

wmayhone
New Contributor III

Do you have devices enrolled in this server? If so how many macOS and iOS?

iVoidWarrantiez
New Contributor III

Yes, 146 macOS, 0 iOS.

Edit: will be adding more macOS this summer and might toss some iOS devices on for testing.

wmayhone
New Contributor III

Is everything running on the one server? 2GB isn't going to cut it, and depending on how often devices are communicating to Jamf Pro, and how many you add, 4GB probably won't be enough either. Have you opened a case with Jamf Support yet to get their recommendations?

hdsreid
Contributor III

The more users you have using the console, enrolled, executing policies, etc, the more ram will be used. 8GB ram is considered the minimum for building home computers at this point, do not be surprised if an enterprise server is going to consume ram like it is going out of style.

Almost as if it using it but not freeing it once done

why would you want it to be freed? having it inactive but still retaining information will make the server run "faster" for users on the web console since it does not have to reload everything in to memory.

I would love to take it down to 2 but 4 is fine

again - why? are you short on memory in your virtual environment? if so, you'll need to expand that or get dedicated hardware for your JSS (or have it cloud hosted if you feel strongly about that). your usage is only going to go up, not down, as you add devices and additional jamf pro users into your environment.

iVoidWarrantiez
New Contributor III

I understand. It would be hard to tell how many users, over 5K students enrolled. I'm not short on memory I am going to keep it at 8gigs. I still have not gone over 5gigs of use but 8 seems to run very well. My host has 64gigs total and I think 20gigs available. Can always add more if needed in the future. Thanks for the replies and information, was helpful.