Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • How do I know that it's the inefficient queries that are the problem, and not the network bandwidth or, say, the fact that the database waits for a lock to be released? Commented Oct 25 at 7:41
  • 2
    @ArseniMourzenko network is not used effectively per OP. A DB lock is indeed a potential origin of a bottleneck (hence a suggestion to vary thread count - the perf will be better on lower thread count if lock is a problem). Commented Oct 25 at 8:09
  • I did not realize the symptoms are described for production system. Current answers are only applicable to a dedicated test setup. Commented Oct 27 at 11:21
  • @Basilevs, often you need to deploy a patch to production with extra logging because you cannot effectively replicate the problem anywhere else. Commented Oct 27 at 23:30
  • @GregBurghardt I know. The advice would be different in that situation though. For example - investigating threading issues would be impossible, due to noise of unrelated requests. Profiling and measuring would be very hard in general. I have no advice for production, besides obvious inspection of slow request's execution plan and review of application code, Commented Oct 28 at 3:48