Update from here...Yesterday afternoon we experienced our first crash since the hotfix about 2.5 weeks ago at about 130PM, and again over night...Everything came back up from this morning fine after doing a hard reset on the boxes. Again, ours seem to happen about 28-33 days and lasts no more then 72 hrs, or less and usually on a Mon or Tues. Now that I know what to do if you can call it that it is not as big a deal. In my world, at least I don't think it's app update.

This thread went dead in November, did everyone get their issues resolved by disabling patch reporting or upgrading to 9.97 or later?

We are having high cpu and memory spikes on our 9.96 install with patch reporting enabled.

@MrRoboto Patch reporting is the problem. I'd turn it off until they fix it. I didn't bother turning it back on after upgrading to 9.99 as I don't think it actually does anything useful right now.

patch reporting bug was fixed with hot fix awhile ago as far as I know. I've been running it with no problem. I think it's better to enable it vs not if you plan to someday use patch in jamf to catch possible issues early.

I enabled Patch Reporting the week after it first became available and we had issues with the JSS within days of enabling PR. If I recall, the issues really started increasing when I started using PR's with smart groups and policies.
Yesterday, I enabled Patch Reporting for three items and the JSS hasn't shown any issues.
- We are at JSS version 9.99.0 and MySQL 5.7.18
- I've only enabled it for three items.
- I haven't yet incorporated the PR into smart groups, scoping, nor policies yet. I am going to wait a few more days before I start using PR for these purposes.

@seann @CasperSally @jhalvorson Thanks!

We upgraded to 9.96 back in December and enabled patch reporting a few couple months later. Started with a few software titles and ended up with 8. Around then the JSS would slow down periodically, things got much worse over the past few weeks. Regular slow downs, high cpu/memory usage, JSS not responding and requiring a reboot every other day. We opened a case with Jamf and was not offered a hot fix for patch reporting (maybe because we are going to upgrade to 9.99 as part of the case), we removed some older smart groups with lots of criteria and bumped up server resources. Things were running better but not perfect, yesterday I disabled patch reporting and watched the cpu time drop from 99% to idling at single digits. Woo hoo, fingers crossed this was the culprit. Will let things settle for a week and then upgrade to 9.99. It was nice having the patch reporting pie charts and alerts but the value stopped there. I am looking forward to Jamf Pro 10 with possible automated patching and revamped Self Service app.