Yeah I've always tried to stagger them and I also make some of them such as search indexing have much longer gaps then the defaults. But some things like the purge users is once a minute so it's pretty much going to sync with every task at some point during the day.

I've examined the histories closely as well and the idea of locked threads does seem a little odd to me. I'd have thought that a server would be able to handle any number of tasks thrown at it.. it would simply do them slower if there are more... like any computer. The idea that one task would lock the server up and cause another to fail just seems weird. The tasks also seem to only take a few milli seconds here and there and again, how can that possibly cause another task to fail.. I mean what are the chances of it.... very confusing.

One thing I've noticed is that if the portal's app pool is set to recycle a lot, there are far fewer errors in the log overall... as if caching or something might cause various problems when the app runs for a longer period.

On another note.. the upgrade to 4.6.2 went flawlessly... so hat's off to Shawn and them for that