CEceohockey60·Mar 5, 2019Submission
TiDB 3.0 Beta Sysbench Results on NVMe SSD
2 points · Open discussionpingcap
docs
Python2016–2019
pingcap / docs
docs
TiDB database documentation. TiDB is an open-source, cloud-native, distributed, MySQL-Compatible database for elastic scale and real-time analytics.
7Distinct people
11Mentions
0Explicit recommenders
616GitHub stars
What to know before exploring
What it is
TiDB database documentation. TiDB is an open-source, cloud-native, distributed, MySQL-Compatible database for elastic scale and real-time analytics.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 11:56:56 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month11 dated mentions
Observed mentions: 2016-10-21 09:35:02 UTC to 2019-03-05 04:22:03 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Oct 2016 | 2016-10-01 00:00:00 UTC | 2016-11-01 00:00:00 UTC | 1 | 1 | 0 |
| Nov 2016 | 2016-11-01 00:00:00 UTC | 2016-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2016 | 2016-12-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2017 | 2017-01-01 00:00:00 UTC | 2017-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2017 | 2017-02-01 00:00:00 UTC | 2017-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2017 | 2017-03-01 00:00:00 UTC | 2017-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2017 | 2017-04-01 00:00:00 UTC | 2017-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2017 | 2017-05-01 00:00:00 UTC | 2017-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2017 | 2017-06-01 00:00:00 UTC | 2017-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2017 | 2017-07-01 00:00:00 UTC | 2017-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2017 | 2017-08-01 00:00:00 UTC | 2017-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2017 | 2017-09-01 00:00:00 UTC | 2017-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2017 | 2017-10-01 00:00:00 UTC | 2017-11-01 00:00:00 UTC | 1 | 0 | 1 |
| Nov 2017 | 2017-11-01 00:00:00 UTC | 2017-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2017 | 2017-12-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 1 | 0 |
| Jan 2018 | 2018-01-01 00:00:00 UTC | 2018-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2018 | 2018-02-01 00:00:00 UTC | 2018-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2018 | 2018-03-01 00:00:00 UTC | 2018-04-01 00:00:00 UTC | 3 | 0 | 3 |
| Apr 2018 | 2018-04-01 00:00:00 UTC | 2018-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2018 | 2018-05-01 00:00:00 UTC | 2018-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2018 | 2018-06-01 00:00:00 UTC | 2018-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2018 | 2018-07-01 00:00:00 UTC | 2018-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2018 | 2018-08-01 00:00:00 UTC | 2018-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2018 | 2018-09-01 00:00:00 UTC | 2018-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2018 | 2018-10-01 00:00:00 UTC | 2018-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2018 | 2018-11-01 00:00:00 UTC | 2018-12-01 00:00:00 UTC | 2 | 0 | 2 |
| Dec 2018 | 2018-12-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 2 | 0 | 2 |
| Jan 2019 | 2019-01-01 00:00:00 UTC | 2019-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2019 | 2019-02-01 00:00:00 UTC | 2019-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2019 | 2019-03-01 00:00:00 UTC | 2019-04-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
11 sourcescuid removes more of the randomness adds a counter and a fingerprint:
https://github.com/ericelliott/cuid
The default id in MongoDB does about the same. I always thought the MongoDB identifiers worked well for a lot of use cases.
Its also worth mentioning that integer incrementing ids can scale just fine if you reserve them in large blocks and they are no longer guaranteed to match insertion order, e.g: https://github.com/pingcap/docs/blob/master/sql/mysql-compat...
In ULID: Universally Unique Lexicographically Sortable IdentifierHey can someone from TiDB help me understand the benchmark results you posted comparing 2.0 with 2.1?
https://github.com/pingcap/docs/blob/master/benchmark/sysben...
The main question is this: how large is the dataset created in Sysbench? 16 tables with 10,000,000 pieces of data per table is interesting, but how big are those individual pieces? Morgan said "the expected data volume for TiDB is larger than memory," so does this benchmark actually test the underlying storage, or is it all in-memory?
Thanks for any help! Would like to try replicating this if possible in our lab.
In TiDB 2.1 GA: Battle-Tested to Handle an Unpredictable WorldInteresting, TiDB also three components [0](KV, DB and PD), I guess this MongoDB layer in FoundationDB is the DB piece of the cluster.
[0] https://github.com/pingcap/docs#tidb-server
In FoundationDB Document LayerGood to see the progress, I was looking at the roadmap page: https://github.com/pingcap/docs/blob/master/ROADMAP.md
Views and CTEs are probably the biggest missing pieces now.
In Progress in performance and scalability with CockroachDBAs a distributed database system, the highly-layered architecture of TiDB is not a disadvantage because it makes TiDB easier to debug and diagnose when issues occur. The complicity resulted from the separated modules can be easily tackled by automatic deployment tools and microservice framework.
For example, TiDB can be easily deployed either using Ansible: https://pingcap.com/docs/op-guide/ansible-deployment/
or Docker Compose:
https://pingcap.com/docs/op-guide/docker-compose/
TiDB has been widely adopted by many users (https://github.com/pingcap/docs/blob/master/adopters.md) in production because it support the best features of both RDBMS and NoSQL. It is quickly evolving and iterating based on users’ requirements which are prioritized and listed on the Roadmap.
In CockroachDB 2.0 Performance Makes Significant StridesThe documentation states that phantom reads are not possible (under the default isolation level or repeatable read): https://github.com/pingcap/docs/blob/master/sql/transaction-...
In CockroachDB 2.0 Performance Makes Significant StridesTiDB is much more complicated to run with several moving pieces. Also missing a lot of standard relational features as you can see from the roadmap: https://github.com/pingcap/docs/blob/master/ROADMAP.md
In CockroachDB 2.0 Performance Makes Significant StridesWe have a document for Docker deployment: https://github.com/pingcap/docs/blob/master/op-guide/docker-...
And we will provide a Kubernetes based deployment solution soon.
In Show HN: TiDB 1.0 is production readyFrequently asked questions about TiDB
2 points · Open discussion