| Gehel added a comment. |
There are multiple issues which can come from oversized heap. In particular:
- If heap is available, it will be used, garbage collection will just start later.
- Graph traversal in not linear (it is O(n) to O(n^2), depending on how cyclic the graphs is), traversing smaller graphs more often can be more efficient than traversing large graphs less often.
- Long full GC pauses, since full GC is run less often, it has to do more once it kicks in (we do see GC pauses of over 30'').
- It makes reasoning about object promotion harder than it should be.
Oversized heap is the main perf issue I have seen with Java applications. I'm not saying it is the only one here. But I would like to ensure that we have a heap reasonably sized before trying other tricks...
TASK DETAIL
EMAIL PREFERENCES
To: Gehel
Cc: Stashbot, gerritbot, Smalyshev, Gehel, Aklapper, Lordiis, Lucas_Werkmeister_WMDE, GoranSMilovanovic, Adik2382, Th3d3v1ls, Ramalepe, Liugev6, QZanden, EBjune, merbst, Avner, Lewizho99, Maathavan, debt, Jonas, FloNight, Xmlizer, Izno, jkroll, Wikidata-bugs, Jdouglas, aude, Tobias1984, Manybubbles, Mbch331
Cc: Stashbot, gerritbot, Smalyshev, Gehel, Aklapper, Lordiis, Lucas_Werkmeister_WMDE, GoranSMilovanovic, Adik2382, Th3d3v1ls, Ramalepe, Liugev6, QZanden, EBjune, merbst, Avner, Lewizho99, Maathavan, debt, Jonas, FloNight, Xmlizer, Izno, jkroll, Wikidata-bugs, Jdouglas, aude, Tobias1984, Manybubbles, Mbch331
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
