Yes, and maybe distribute the report creation around the hour. If you have a report with numerous nbr of tables involved, a heave reading of the db occurs. Even if there is no writing to the db, a number of threads are started. Since we do not really know where the limit of concurrent running threads are (especially inside a VM), I think you can adjust the upper limit until we see the "old" problem coming back.But I guess I may have to go down on the frequency of logging in the end.
Since the Q goes up that high, I fear that there are some threads that are not terminating correctly (could be threads used for report creation).
But spreading the execution a bit would not harm...
The queue is up to 41 now, it seems to keep growing even when I'm only running one report and video at the same time. I guess I'll have to increase the size of the queue to around 100! Would that be dangerous? The video conversion is only taking about 20 minutes, and I do them 3-4 times a day.
Which in my opinion is all a Volvo is useful for... I'd rather have a Koenigsegg! But seriously, this is work, not amusement. That means that when I'm at the cabin it has to be easily accessible from both home (when my wife works from home) and the cabin. I have fiber at home, bad DSL at the cabin, so sending to the cabin is fast, the other way is 1/50 of the speed... It's down to 20 now.