We are having a bit of an issue, where resuming failed tasks takes minutes to do.
Attached is a camtasia
Looks like it’s a result of a long read queue because mongo is backed up. I imagine it should return to normal once mongo has caught up. Definitely need to look at ways to get the load down on mongo.
The load on mongo will just get worse with beta10+, correct?
I don’t think it will. At first, we were concerned that the Monitor might be hitting the database too quickly with UI speed improvements we made, but the actual interval that the Monitor talks to Mongo shouldn’t change. You can actually dial that interval up in the Repository Options as well under Monitor Settings.