*: refactor transaction documents#2198
Conversation
|
@dcalvin Please resolve lint failure. |
@anotherrachel will follow this PR through. |
9e493de to
60d1902
Compare
youjiali1995
left a comment
There was a problem hiding this comment.
Thanks @dcalvin . 由于 TiDB 事务模型变化较大,后面我们研发同学也会进行一波整理。这个 PR 处理掉 comments 后我觉得是可以的。
|
@lilin90 PTAL again, thanks! If the content is ready, I'll update other versions next. |
|
All versions updated. Some changes are not applicable for v2.1. |
| > | ||
| > 由于 TiDB 中的资源是分布式的,TiDB 中单线程 workload 可能不会很好地利用分布式资源,因此性能相比于单实例部署的 MySQL 较低。这与 TiDB 中的事务延迟较高的情況类似。 | ||
|
|
||
| ### 大事务 |
There was a problem hiding this comment.
This confuses me... The doc that introduces transaction model (now deleted in this PR) used to say "大事务“, even in v2.1. See here.
So "大事务“ cannot be used here in v2.1 v3.0 and v3.1? @youjiali1995
There was a problem hiding this comment.
@anotherrachel The documentation are actually telling the user that TiDB has poor support of big transactions so there are some limitations.
There was a problem hiding this comment.
The limitations are relaxed in 4.0 so we say big transactions are supported in 4.0
|
@anotherrachel Please update this PR according to #2255, thanks! |
549b048 to
d55f8f4
Compare
|
@lilin90 PTAL, thanks! |
What is changed, added or deleted?
Based on our reviews and offline discussions, we decided to refactor and update transaction-related documents, including:
@anotherrachel FYI.
What is the related PR or file link(s)?
Which TiDB version(s) does your changes apply to?
Note: If your changes apply to multiple TiDB versions, make sure you update the documents in the corresponding version folders such as "dev", "v3.0", "v2.1" and "v3.1" in this PR.