TopSQL & statement summary use a lot of memory

[zyguan]

General Question

We test tidb with sqllogic daily and it fails recently. The case fails because the tidb gets OOM killed and it seems that the memory is maily used by topsql & statement summary.

heap-dump.tar.gz

[zyguan]

/cc @breezewish

[mornyx]

Hi @zyguan, could you please provide the version & commit id of this TiDB instance? Also includes the num of CPU cores and memory size of the machine.

[zyguan]

Hi @zyguan, could you please provide the version & commit id of this TiDB instance? Also includes the num of CPU cores and memory size of the machine.

The latest master is used and resource quotas described here.

[mornyx]

The latest master is used and resource quotas described here.

Did you turn on the TopSQL during the test?

[zyguan]

The latest master is used and resource quotas described here.

Did you turn on the TopSQL during the test?

No special settings for enabling TopSQL, it shall be disabled by default.

[mornyx]

#34558 has been merged, so the green part should have been resolved. Whether the blue part will cause the leak is still unclear, so we need to continue to observe the next daily test report. cc @zyguan

[mornyx]

Whether the blue part will cause the leak is still unclear, so we need to continue to observe the next daily test report.

Does the memory leak still exist in the latest test? I see that the sqllogic tests on TCMS all seem to succeed.

[zyguan]

Whether the blue part will cause the leak is still unclear, so we need to continue to observe the next daily test report.

Does the memory leak still exist in the latest test? I see that the sqllogic tests on TCMS all seem to succeed.

No, no OOM recently. It’s ok now.