| Gehel added a comment. |
The thread dumps are interesting!
F17602509: threads-2018-05-02-16:05:59.log
at 16:05, I can see
- 479 threads waiting in thread pools. Most of them from the com.bigdata.journal.Journal.executorService thread pool and a few in an unnamed pool. That's at least a very inefficient use of resources, even if probably not an immediate issue.
- 20 threads in epollWait(), all in the jetty HttpClient pool. My guess is that this pool is related to MWApiServiceCall or maybe GeoService. Since at least in MWApiServiceCall we are using the HTTP client synchronously, we could get rid of that thread pool entirely.
- 20 threads waiting in a qtp1464642111 thread pool. This is a Jetty QueuedThreadPool, but not sure yet where it is used.
- 10 threads waiting for various locks while processing ChunkedRunningQuery. This indicates a live lock issue, but might or might not be serious.
F17602512: threads-2018-05-02-17:05:00.log
This second thread dump is similar.
I'll wait for a few more thread dumps and see if I can find other patterns.
TASK DETAIL
EMAIL PREFERENCES
To: Gehel
Cc: Smalyshev, Gehel, Aklapper, Lucas_Werkmeister_WMDE, Jonas, jkroll, Wikidata-bugs, Jdouglas, aude, Tobias1984, Manybubbles
Cc: Smalyshev, Gehel, Aklapper, Lucas_Werkmeister_WMDE, Jonas, jkroll, Wikidata-bugs, Jdouglas, aude, Tobias1984, Manybubbles
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
