SP2013 Enterprise, separate SQL 2012 server, single server farm, ~150 users
The local SP farm has been extremely overtaxed lately (24/7) and I can't figure out why. Here's a shot of what the resource usage looks like:
The Timer Service in particular seems to eat up most of the resources, at times up to 75% of the CPU and 80% of the memory just by iteself. This is a pretty small deployment with nothing crazy going on, and at the time this shot was taken there are no active crawls or other events that should be taking up this kind of juice. This server has 4 virtual cores at 2.4GHz and 20 GB of memory, so I don't get why it's choking so hard on simply idling. Can anyone spot the problem here? I don't know enough about what processes should be taking up to determine if anything in that list is disproportional. Until the past month this server was humming along just fine, and as far as I know the amount of resources allotted to the server should be way more than enough to run it.
Edit: As requested, here is a peek into the ULS log showing what the OWSTIMER.EXE process is doing. These events are occurring a couple times a second, sometimes more:
UpdatedConcurrencyException: The object UserProfileImportJob Name=User Profile Service Application_ProfileImportJob was updated by another user. Determine if these changes will conflict, resolve any differences, and reapply the second change. This error may also indicate a programming error caused by obtaining two copies of the same object in a single thread. Previous update information: User: [domain\farm_admin_account] Process:OWSTIMER (2004) Machine:[server] Time:September 11, 2014 09:20:44.0000 Current update information: User: [domain\farm_admin_account] Process:OWSTIMER (2012) Machine:[server] Time:September 15, 2014 12:46:39.1883 ConcurrencyException: Old Version : 5202587 New Version : 5202587