*: upgrade golang to 1.25.x

[solotzg]

What problem does this PR solve?

Issue Number: close #62981
Issue Number: ref #62487

• From go 1.24.0 golang's switch its builtin map to swiss table: https://go.dev/blog/swisstable.
• TiDB manually estimates a map's memory usage for memory control, since the implementation of map is changed, we need adopt the memory estimation for the new map.
• CRDB uses another specified variables allocator to allocate and release memory used by a Map.
  • Such allocator is supposed to have the ability to record memory usage info.

What changed and how does it work?

Solution

• Remove all bInMap and calculate approximate heap size dynamically
  • Capacity of swisstable is 1024(maxTableCapacity) which means the overhead of split(rehash) is quite low
  • It is difficult to simply determine the timing of each swisstable split(growthLeft == 0) when dirLen is large
• Opportunities to recalculate size:
  • Increment of max len reaches 1024 or double len
  • Approximate size: groupSize * maxLen * 204 / 1000
    • 204: linear fitting of different kinds of map[K]V
• Sampling statistics of heap size:
  • calculate approximate valid swisstable number & total heap size of map
• Check abi each time then modify func checkMapABI before upgrading golang version

TODO

• Upgrade client_golang and testify(some unit tests will break if using testify @ v1.11.1).

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Benchmark

TPC-H

ENV:

• tidb x 1: 4c 20g
• pd x 1, tikv x 1
• TPC-H (sf 8)
• set global tidb_mem_quota_query=20<<30

TPC-H (sf 8)	go1.23.12	go1.25.x
Q1	6.07	6.07
Q2	1.58	1.31
Q3	2.99	2.92
Q4	1.24	1.17
Q5	4.73	4.6
Q6	2.52	2.72
Q7	3.99	3.93
Q8	2.05	1.98
Q9	8.56	8.29
Q10	2.25	2.18
Q11	1.24	1.11
Q12	4.19	4.13
Q13	4.87	4.19
Q14	3.12	2.92
Q15	5.6	5.67
Q16	1.24	1.31
Q17	12.99	13.59
Q18	14.66	15.33
Q19	6.07	6.21
Q20	3.19	3.12
Q21	5.34	5.2
Q22	1.44	1.38
SUM	99.93	99.33

TPC-C

Env:

• tidb: 4c 2g
  • no copr-cache
• pd x 1, tikv x 1

go1.23.12

• warehouses: 4, threads: 100, duration: 3m
  • tpmC: 22262.8, tpmTotal: 49279.3, efficiency: 43279.1%
• warehouses: 4, threads: 200, duration: 3m
  • tpmC: 18614.0, tpmTotal: 41521.7, efficiency: 36185.8%
  • Error 8176: kill the top-1 SQL

go1.25.x

• warehouses: 4, threads: 100, duration: 3m
  • tpmC: 22944.3, tpmTotal: 50980.4, efficiency: 44604.0%
• warehouses: 4, threads: 200, duration: 3m
  • tpmC: 20613.8, tpmTotal: 45561.0, efficiency: 40073.5%
  • Error 8176: kill the top-1 SQL

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[tiprow]

Hi @solotzg. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[solotzg]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: hawkingrei, windtalker, xzhangxian1008
Once this PR has been reviewed and has the lgtm label, please assign bb7133, d3hunter for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS [hawkingrei,windtalker]

  Need more approvers for rest parts.

• dumpling/OWNERS
• pkg/parser/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment