On Thu, 21 Jan 2016, John Klos wrote:
Ideas about why this is so busy?
No. However, you could try to profile it to find out. Run it in ktrace(1) and/or do a gdb -attach to it's PID. Then start looking at the trace output to see what kind of library functions it's running in it's main event loop. Use kdump to view the ktrace output. That may give you some idea.
If you've already tried that... there is always fprintf() logging statements stuffed in the code in key places to see what bits of logic are getting the most action.
Swift