It's been a challenge keeping our JSS stable with just 12k Mac. I run into different performance issue that results in service outages at the rate of at least once a month. The solution is usually "upgrade to the latest version" or "have you though about moving to jamf cloud?". :)
I don't know how performance is officially measured by Jamf... We defined performance internally as the JSS's ability to process client connections. This measurement does not really apply to the JSS web UI performance, which has always been "slow" when compared to other admin consoles I use.
We have an internal dashboard for tracking simultaneous TCP connections to the JSS' client port, open files on the server, and most importantly: the number of TCP connections in a "CLOSED_WAIT" status. We know when we see a sharp spike in CLOSED_WAIT connections, the JSS is struggling to keep up with client requests and a tomcat crash is imminent. We found the host server resources are not taxed and rarely exceeds 50% total resource usage for CPU/RAM/IO. Tomcat crashes out long before the server runs out of resources, so this metric is not tracked in the dashboard.
Our JSS has 2 app servers (DMZ+LAN) on a pair of MacPros, I have a script running on each that outputs stats to a live web dashboard. The script I use it below for reference, the dashboard is using a local implementation of http://dygraphs.com for a live JSS "Heartbeat"
The script also has an option for reloading tomcat if a certain threshold is reached. This has saved me as tomcat will not recover on its own once crashed.
JSS statistics: weekly inventory, hourly checkin, Application usage tracking enabled, 20+ EAs, several config profiles, 400 policies, ~100 self service policies, ~3000 network segments, 1200 buildings, 300 departments, 250 smart groups, 50 licensed app objects, LDAP, etc...
MacPro "server" config: 12core xeon, 32GB RAM, 1TB SSD, 10GB fiber optic network link over TB2.
Normally my JSS runs an average of 150 simultaneous client connection over port 8443. mySQL: ~50% CPU and Java: ~90% CPU 6GB RAM.
At business day start, it not uncommon to see 300-400 simultaneous connections to the JSS. mySQL: ~150% CPU and Java: ~250% CPU 8GB RAM.
During off hours, the JSS has 20-30 simultaneous connections. mySQL: ~10% CPU and Java: ~25% CPU 6GB RAM.
Tomcat starts to destabilize around 1700 connections and hard crashes at 2200 connections. mySQL: ~250% CPU and Java: ~250-900% CPU.
mySQL is on the same server as the master tomcat app. We've found ~25GB of data is passed locally between tomcat and mySQL over the course of a normal business day.
#!/bin/bash
# date, number of TCP connections on port 8443, number of connections in closed_wait, number of open files, hostname
while [ 1 ]; do
sleep 5
closed_wait="$(netstat -f inet -n | grep 8443 | grep CLOSE_ | awk '{print $5}' | wc -l | awk '{print $1}')"
result="$("$(date "+%Y-%m-%d %H:%M:%S"), $(netstat -f inet -n | grep -i 8443 | wc -l | awk '{print $1}'), ${closed_wait}, $(sysctl kern.num_files | awk '{print $2}'),$(hostname)")"
echo "${result}" >> /Library/Logs/JSS/TCPConnectionLogs/Casper_TCP_connecions$(date "+%Y%m%d").log
if [ "${closed_wait}" -ge "1500" ]; then
echo "$(date): CLOSED WAIT COUNT OVER 1500!! RESTARTING TOMCAT" >> /Library/Logs/JSS/kicked.the.cat.log
launchctl unload /Library/LaunchDaemons/com.jamfsoftware.tomcat.plist
sleep 2
launchctl load /Library/LaunchDaemons/com.jamfsoftware.tomcat.plist
fi
done
exit 0
