releases: add release note for v8.0.0 #16664
Conversation
ti-chi-bot
bot
added
contribution
hfxsd
added
translation/doing
ti-chi-bot
bot
added
the
size/L
add desc of Acceleration of Cluster Snapshot Restore Speed ( GA )
add description for Enabling ObjectLock on AWS S3 Log Backup
releases/release-8.0.0.md
Outdated
| 更多信息，请参考[用户文档](链接)。 | ||
| * BR 快照恢复速度最高提升 10 倍 GA [#issue号](链接) @[3pointer](https://github.com/3pointer) | ||
|
|
||
| TiDB v8.0.0 版本起，通过对 Region 打散算法进行性能优化和改进，在确保数据充分打散的前提下，快照恢复提速的改进功能正式 GA，并默认启用。这一改进不仅充分利用了每个 TiKV 节点资源并行恢复，还确保了每个 TiKV 节点的数据恢复速度达到机器资源容许的最大值。在实际案例中，单 TiKV 节点的数据恢复速度稳定在 1.2 GB/s，并且能够在 1 小时内完成对 100 TB 数据的恢复。 |
There was a problem hiding this comment.
| TiDB v8.0.0 版本起，通过对 Region 打散算法进行性能优化和改进，在确保数据充分打散的前提下，快照恢复提速的改进功能正式 GA，并默认启用。这一改进不仅充分利用了每个 TiKV 节点资源并行恢复，还确保了每个 TiKV 节点的数据恢复速度达到机器资源容许的最大值。在实际案例中，单 TiKV 节点的数据恢复速度稳定在 1.2 GB/s，并且能够在 1 小时内完成对 100 TB 数据的恢复。 | |
| TiDB v8.0.0 版本起，通过对 Region 打散算法进行性能优化和改进在确保数据充分打散的前提下，快照恢复提速的改进功能正式 GA，并默认启用。这一改进不仅充分利用了每个 TiKV 节点资源并行恢复，还确保了每个 TiKV 节点的数据恢复速度达到机器资源容许的最大值。在实际案例中，单 TiKV 节点的数据恢复速度稳定在 1.2 GB/s，并且能够在 1 小时内完成对 100 TB 数据的恢复。 |
| TiDB v8.0.0 版本起，通过对 Region 打散算法进行性能优化和改进，在确保数据充分打散的前提下，快照恢复提速的改进功能正式 GA，并默认启用。这一改进不仅充分利用了每个 TiKV 节点资源并行恢复，还确保了每个 TiKV 节点的数据恢复速度达到机器资源容许的最大值。在实际案例中，单 TiKV 节点的数据恢复速度稳定在 1.2 GB/s，并且能够在 1 小时内完成对 100 TB 数据的恢复。 | |
| TiDB v8.0.0 版本起，通过对 Region 打散算法进行性能优化和改进，减少 sst 文件下载和 ingest 相互影响, 提升 ddl 执行效率, 提升统计信息恢复效率等措施后, 在保持数据充分打散的前提下，快照恢复提速的改进功能正式 GA，并默认启用。这一改进充分利用了每个 TiKV 节点资源并行恢复，使得每个 TiKV 节点的数据恢复能充分利用和硬件的磁盘和网络带宽。在实际案例中，单 TiKV 节点的数据恢复速度稳定在 1.2 GB/s，并且能够在 1 小时内完成对 100 TB 数据的恢复。 |
There was a problem hiding this comment.
TiDB v8.0.0 版本开始，通过对 Region 打散算法进行性能优化和改进，成功减少了 SST 文件下载和 Ingest 进程之间的相互影响，提升了 DDL 执行效率和统计信息恢复效率等。这些措施充分利用了每个 TiKV 节点的资源进行并行恢复，大幅提升了恢复速度。在实际案例中，单个 TiKV 节点的数据恢复速度稳定在 1.2 GB/s，并且能够在 1 小时内完成对 100 TB 数据的恢复。这项改进功能已在 TiDB v8.0.0 版本正式发布并默认启用。
add description of PITR Supports Backing Up Data Imported via Lightning Physical Mode
Co-authored-by: BornChanger <[email protected]>
Co-authored-by: xixirangrang <[email protected]>
|
@ljun0712: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: 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/test-infra repository. |
|
@Frank945946: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: 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/test-infra repository. |
Co-authored-by: Grace Cai <[email protected]>
Co-authored-by: Grace Cai <[email protected]>
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hfxsd The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
In response to a cherrypick label: new pull request created to branch |
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?