Skip to content
Permalink
Browse files

*: Move remaining docs to version specific directories (#1207)

Prepare for version-split.
  • Loading branch information...
morgo committed Jun 14, 2019
1 parent dee26aa commit 104aabf9a76f29f391c25cd10ebb13f2597db711
Showing with 619 additions and 663 deletions.
  1. +321 −321 TOC.md
  2. +0 −15 dev-guide/deployment.md
  3. +0 −68 dev-guide/development.md
  4. +0 −29 dev-guide/requirements.md
  5. +1 −0 { → dev}/adopters.md
  6. +2 −1 { → dev}/architecture.md
  7. +4 −3 { → dev}/benchmark/dm-v1-alpha.md
  8. +4 −3 { → dev}/benchmark/how-to-run-sysbench.md
  9. +1 −0 { → dev}/benchmark/sysbench-v2.md
  10. +4 −3 { → dev}/benchmark/sysbench-v3.md
  11. +10 −9 { → dev}/benchmark/sysbench.md
  12. +2 −1 { → dev}/benchmark/tpch-v2.md
  13. +2 −1 { → dev}/benchmark/tpch.md
  14. +1 −0 { → dev}/community.md
  15. +1 −0 { → dev}/contribute.md
  16. 0 { → dev}/etc/DiskPerformance.json
  17. 0 { → dev}/etc/Drainer.json
  18. 0 { → dev}/etc/Syncer.json
  19. 0 { → dev}/etc/node.json
  20. 0 { → dev}/etc/overview.json
  21. 0 { → dev}/etc/pd.json
  22. 0 { → dev}/etc/tidb.json
  23. 0 { → dev}/etc/tikv.json
  24. +3 −3 { → dev}/faq/tidb-lightning.md
  25. +53 −55 { → dev}/faq/tidb.md
  26. +1 −1 { → dev}/faq/upgrade.md
  27. +4 −4 dev/how-to/get-started/tidb-binlog.md
  28. +1 −1 dev/how-to/maintain/identify-slow-queries.md
  29. +1 −1 dev/how-to/monitor/overview.md
  30. +3 −3 dev/how-to/secure/enable-tls-clients.md
  31. +1 −1 dev/how-to/troubleshoot/cluster-setup.md
  32. +3 −3 dev/how-to/troubleshoot/data-migration.md
  33. +3 −2 { → dev}/key-features.md
  34. +39 −0 dev/overview.md
  35. +1 −1 dev/reference/configuration/tidb-server/configuration.md
  36. +3 −2 dev/reference/error-codes.md
  37. +1 −1 dev/reference/mysql-compatibility.md
  38. +2 −2 dev/reference/sql/statements/kill.md
  39. +1 −1 dev/reference/tools/data-migration/overview.md
  40. +1 −1 dev/reference/tools/download.md
  41. +2 −2 dev/reference/tools/tidb-lightning/deployment.md
  42. +1 −0 { → dev}/releases/101.md
  43. +1 −0 { → dev}/releases/102.md
  44. +1 −0 { → dev}/releases/103.md
  45. +1 −0 { → dev}/releases/104.md
  46. +1 −0 { → dev}/releases/105.md
  47. +1 −0 { → dev}/releases/106.md
  48. +1 −0 { → dev}/releases/107.md
  49. +1 −0 { → dev}/releases/108.md
  50. +1 −0 { → dev}/releases/11alpha.md
  51. +1 −0 { → dev}/releases/11beta.md
  52. +1 −0 { → dev}/releases/2.0.10.md
  53. +1 −0 { → dev}/releases/2.0.11.md
  54. +1 −0 { → dev}/releases/2.0ga.md
  55. +1 −0 { → dev}/releases/2.1.1.md
  56. +1 −0 { → dev}/releases/2.1.10.md
  57. +1 −0 { → dev}/releases/2.1.11.md
  58. 0 { → dev}/releases/2.1.12.md
  59. +1 −0 { → dev}/releases/2.1.2.md
  60. +1 −0 { → dev}/releases/2.1.3.md
  61. +1 −0 { → dev}/releases/2.1.4.md
  62. +1 −0 { → dev}/releases/2.1.5.md
  63. +1 −0 { → dev}/releases/2.1.6.md
  64. +1 −0 { → dev}/releases/2.1.7.md
  65. +1 −0 { → dev}/releases/2.1.8.md
  66. +1 −0 { → dev}/releases/2.1.9.md
  67. +9 −8 { → dev}/releases/2.1ga.md
  68. +1 −0 { → dev}/releases/201.md
  69. +1 −0 { → dev}/releases/202.md
  70. +1 −0 { → dev}/releases/203.md
  71. +1 −0 { → dev}/releases/204.md
  72. +1 −0 { → dev}/releases/205.md
  73. +1 −0 { → dev}/releases/206.md
  74. +1 −0 { → dev}/releases/207.md
  75. +1 −0 { → dev}/releases/208.md
  76. +1 −0 { → dev}/releases/209.md
  77. +1 −0 { → dev}/releases/21beta.md
  78. +1 −0 { → dev}/releases/21rc1.md
  79. +1 −0 { → dev}/releases/21rc2.md
  80. +1 −0 { → dev}/releases/21rc3.md
  81. +1 −0 { → dev}/releases/21rc4.md
  82. +1 −0 { → dev}/releases/21rc5.md
  83. +1 −0 { → dev}/releases/2rc1.md
  84. +1 −0 { → dev}/releases/2rc3.md
  85. +1 −0 { → dev}/releases/2rc4.md
  86. +1 −0 { → dev}/releases/2rc5.md
  87. +1 −0 { → dev}/releases/3.0.0-beta.1.md
  88. +1 −0 { → dev}/releases/3.0.0-rc.1.md
  89. +1 −0 { → dev}/releases/3.0.0-rc.2.md
  90. +1 −0 { → dev}/releases/3.0beta.md
  91. +1 −0 { → dev}/releases/ga.md
  92. +1 −0 { → dev}/releases/prega.md
  93. +1 −0 { → dev}/releases/rc1.md
  94. +1 −0 { → dev}/releases/rc2.md
  95. +1 −0 { → dev}/releases/rc3.md
  96. +1 −0 { → dev}/releases/rc4.md
  97. +74 −0 dev/releases/rn.md
  98. +1 −0 { → dev}/report-issue.md
  99. +1 −1 { → dev}/roadmap.md
  100. +1 −1 { → dev}/support-resources.md
  101. +1 −0 { → dev}/technical-writing-project-ideas.md
  102. +1 −1 { → dev}/tispark/tispark-quick-start-guide_v1.x.md
  103. +2 −2 { → dev}/tispark/tispark-user-guide_v1.x.md
  104. +0 −39 overview.md
  105. +0 −73 releases/rn.md
642 TOC.md

Large diffs are not rendered by default.

This file was deleted.

This file was deleted.

This file was deleted.

@@ -2,6 +2,7 @@
title: TiDB Adopters
summary: Learn about the list of TiDB adopters in various industries.
category: adopters
aliases: ['/docs/adopters/']
---

# TiDB Adopters
@@ -2,13 +2,14 @@
title: TiDB Architecture
summary: The key architecture components of the TiDB platform
category: introduction
aliases: ['/docs/architecture/']
---

# TiDB Architecture

The TiDB platform is comprised of three key components: the TiDB server, the PD server, and the TiKV server. In addition, TiDB also provides the [TiSpark](https://github.com/pingcap/tispark/) component for complex OLAP requirements.

![image alt text](media/tidb-architecture.png)
![image alt text](/media/tidb-architecture.png)

## TiDB server

@@ -2,6 +2,7 @@
title: DM Benchmark Report
summary: Learn about the DM benchmark report.
category: benchmark
aliases: ['/docs/benchmark/dm-v1-alpha/']
---

# DM Benchmark Report
@@ -126,9 +127,9 @@ syncer:

#### DM key indicator monitor

![](../media/dm-benchmark-01.png)
![](/media/dm-benchmark-01.png)

#### TiDB key indicator monitor

![](../media/dm-benchmark-02.png)
![](../media/dm-benchmark-03.png)
![](/media/dm-benchmark-02.png)
![](/media/dm-benchmark-03.png)
@@ -1,6 +1,7 @@
---
title: How to Test TiDB Using Sysbench
category: benchmark
aliases: ['/docs/benchmark/sysbench-v4/','/docs/benchmark/how-to-run-sysbench.md']
---

# How to Test TiDB Using Sysbench
@@ -9,9 +10,9 @@ In this test, Sysbench 1.0.14 and TiDB 3.0 Beta are used. It is recommended to u

## Test environment

- [Hardware requirements](https://pingcap.com/docs/op-guide/recommendation/)
- [Hardware recommendations](/dev/how-to/deploy/hardware-recommendations.md)

- The TiDB cluster is deployed according to the [TiDB Deployment Guide](https://pingcap.com/docs/op-guide/ansible-deployment/). Suppose there are 3 servers in total. It is recommended to deploy 1 TiDB instance, 1 PD instance and 1 TiKV instance on each server. As for disk space, supposing that there are 32 tables and 10M rows of data on each table, it is recommended that the disk space where TiKV's data directory resides is larger than 512 GB.
- The TiDB cluster is deployed according to the [TiDB Deployment Guide](/dev/how-to/deploy/orchestrated/ansible.md). Suppose there are 3 servers in total. It is recommended to deploy 1 TiDB instance, 1 PD instance and 1 TiKV instance on each server. As for disk space, supposing that there are 32 tables and 10M rows of data on each table, it is recommended that the disk space where TiKV's data directory resides is larger than 512 GB.
The number of concurrent connections to a single TiDB cluster is recommended to be under 500. If you need to increase the concurrency pressure on the entire system, you can add TiDB instances to the cluster whose number depends on the pressure of the test.

IDC machines:
@@ -76,7 +77,7 @@ block-cache-size = "24GB"
block-cache-size = "6GB"
```

For more detailed information on TiKV performance tuning, see [Tune TiKV Performance](https://pingcap.com/docs/op-guide/tune-tikv/).
For more detailed information on TiKV performance tuning, see [Tune TiKV Performance](/dev/reference/performance/tune-tikv.md).

## Test process

@@ -1,6 +1,7 @@
---
title: TiDB Sysbench Performance Test Report -- v2.0.0 vs. v1.0.0
category: benchmark
aliases: ['/docs/benchmark/sysbench-v2/']
---

# TiDB Sysbench Performance Test Report -- v2.0.0 vs. v1.0.0
@@ -1,6 +1,7 @@
---
title: TiDB Sysbench Performance Test Report -- v2.1 vs. v2.0
category: benchmark
aliases: ['/docs/benchmark/sysbench-v3/']
---

# TiDB Sysbench Performance Test Report -- v2.1 vs. v2.0
@@ -99,7 +100,7 @@ block-cache-size = "20GB"
| v2.0 | 512 | 121350.61 | 11.65 |
| v2.0 | 1024 | 150036.31 | 17.32 |

![point select](../media/sysbench_v3_point_select.png)
![point select](/media/sysbench_v3_point_select.png)

According to the statistics above, the `Point Select` query performance of TiDB 2.1 has increased by **50%** than that of TiDB 2.0.

@@ -118,7 +119,7 @@ According to the statistics above, the `Point Select` query performance of TiDB
| v2.0 | 512 | 25994.33 | 46.63 |
| v2.0 | 1024 | 27917.52 | 92.42 |

![update non-index](../media/sysbench_v3_update_non_index.png)
![update non-index](/media/sysbench_v3_update_non_index.png)

According to the statistics above, the `Update Non-Index` write performance of TiDB 2.1 and TiDB 2.0 is almost the same.

@@ -137,6 +138,6 @@ According to the statistics above, the `Update Non-Index` write performance of T
| v2.0 | 512 | 11162.63 | 104.84 |
| v2.0 | 1024 | 12067.63 | 179.94 |

![update index](../media/sysbench_v3_update_index.png)
![update index](/media/sysbench_v3_update_index.png)

According to the statistics above, the `Update Index` write performance of TiDB 2.1 and TiDB 2.0 is almost the same.
@@ -2,6 +2,7 @@
title: Performance test result for TiDB using Sysbench
category: benchmark
draft: true
aliases: ['/docs/benchmark/sysbench/']
---

# Performance test result for TiDB using Sysbench
@@ -111,9 +112,9 @@ max_connections = 2000
| Mysql | 32 | 5 million | 256 | 1902 | 38045 | 134.56 ms / 363.18 ms |
| Mysql | 32 | 10 million | 256 | 1770 | 35416 | 144.55 ms / 383.33 ms |

![](../media/sysbench-01.png)
![](/media/sysbench-01.png)

![](../media/sysbench-02.png)
![](/media/sysbench-02.png)

- `Select` RW test

@@ -130,9 +131,9 @@ max_connections = 2000
| Mysql | 32 | 5 million | 256 | 386866 | 0.66 ms / 1.64 ms |
| Mysql | 32 | 10 million | 256 | 388273 | 0.66 ms / 1.64 ms |

![](../media/sysbench-03.png)
![](/media/sysbench-03.png)

![](../media/sysbench-04.png)
![](/media/sysbench-04.png)

- `Insert` RW test

@@ -149,9 +150,9 @@ max_connections = 2000
| Mysql | 32 | 5 million | 256 | 10593 | 24.16 ms / 82.96 ms |
| Mysql | 32 | 10 million | 256 | 9813 | 26.08 ms / 94.10 ms |

![](../media/sysbench-05.png)
![](/media/sysbench-05.png)

![](../media/sysbench-06.png)
![](/media/sysbench-06.png)

### Scenario two: TiDB horizontal scalability test

@@ -188,7 +189,7 @@ block-cache-size = "2GB"
| 4 TiDB physical nodes | 32 | 1 million | 256 * 4 | 8984 | 179692 | 114.96 ms / 176.73 ms |
| 6 TiDB physical nodes | 32 | 5 million | 256 * 6 | 12953 | 259072 | 117.80 ms / 200.47 ms |

![](../media/sysbench-07.png)
![](/media/sysbench-07.png)

- `Select` RW test

@@ -199,7 +200,7 @@ block-cache-size = "2GB"
| 4 TiDB physical nodes | 32 | 1 million | 256 * 4 | 289933 | 3.53 ms / 8.74 ms |
| 6 TiDB physical nodes | 32 | 5 million | 256 * 6 | 435313 | 3.55 ms / 9.17 ms |

![](../media/sysbench-08.png)
![](/media/sysbench-08.png)

- `Insert` RW test

@@ -209,4 +210,4 @@ block-cache-size = "2GB"
| 5 TiKV physical nodes | 32 | 1 million | 256 * 3 | 60689 | 37.96 ms / 29.9 ms |
| 7 TiKV physical nodes | 32 | 1 million | 256 * 3 | 80087 | 9.62 ms / 21.37 ms |

![](../media/sysbench-09.png)
![](/media/sysbench-09.png)
@@ -1,6 +1,7 @@
---
title: TiDB TPC-H 50G Performance Test Report V2.1
category: benchmark
aliases: ['/docs/benchmark/tpch-v2/']
---

# TiDB TPC-H 50G Performance Test Report V2.1
@@ -96,7 +97,7 @@ TiDB 2.1:
| 21 | 389.883709908s | 361.034544945s |
| 22 | 64.0494630337s | 65.7153418064s |

![TPC-H Query Result](../media/tpch-query-result-v2.png)
![TPC-H Query Result](/media/tpch-query-result-v2.png)

It should be noted that:

@@ -1,6 +1,7 @@
---
title: TiDB TPC-H 50G Performance Test Report V2.0
category: benchmark
aliases: ['/docs/benchmark/tpch/']
---

# TiDB TPC-H 50G Performance Test Report
@@ -98,7 +99,7 @@ TiDB 2.0:
| 21 | 31.466s | OOM |
| 22 | 31.539s | 125.471s |

![TPC-H Query Result](../media/tpch-query-result.png)
![TPC-H Query Result](/media/tpch-query-result.png)

It should be noted that:

@@ -2,6 +2,7 @@
title: Connect with us
summary: Learn about how to connect with us.
category: community
aliases: ['/docs/community/']
---

# Connect with us
@@ -2,6 +2,7 @@
title: Contribute
summary: Learn how to contribute to the TiDB database.
category: how-to
aliases: ['/docs/contribute/']
---

# Contribute
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
@@ -2,7 +2,7 @@
title: TiDB-Lightning FAQ
summary: Learn about the frequently asked questions (FAQs) and answers about TiDB-Lightning.
category: faq
aliases: ['/docs/tools/lightning/faq/']
aliases: ['/docs/tools/lightning/faq/','/docs/faq/tidb-lightning/']
---

# TiDB-Lightning FAQ
@@ -53,8 +53,8 @@ mysql> ADMIN CHECKSUM TABLE `schema`.`table`;
## What kind of data source format is supported by Lightning?

In version 2.1.6, TiDB-Lightning only supports the SQL dump generated by
[mydumper](/tools/mydumper.md)
or [CSV files](/tools/lightning/csv.md) stored in the local filesystem.
[mydumper](/dev/reference/tools/mydumper.md)
or [CSV files](/dev/reference/tools/tidb-lightning/csv.md) stored in the local filesystem.

## Could Lightning skip creating schema and tables?

0 comments on commit 104aabf

Please sign in to comment.
You can’t perform that action at this time.