shenli3514

13 ms·

1. 181.▲
   by shenli3514 9y ago

   >Of the list, AngularJS and MySQL have been the only ones to give us scaling problems. Our monolithic AngularJS code-bundle has got too big and the initial download takes quite a while and the application is a bit too slow. MySQL (in RDS
2. 182.▲
   by shenli3514 9y ago

   We use different isolation levels and priorities for OLAP and OLTP workload.
3. 183.▲
   by shenli3514 9y ago

   We will release a new benchmark result soon.
4. 184.▲
   by shenli3514 9y ago

   I mean the raft/mvcc/transaction layer which are on top of RocksDB and below the SQL layer.
5. 185.▲
   by shenli3514 9y ago

   There are some key differences between TiDB and Cockroach. 1. User interface and eco-system Despite that TiDB and CockroachDB both support SQL, TiDB is compatible with MySQL protocol while Cockroach chooses PostgreSQL. You can directly con
6. 186.▲
   by shenli3514 9y ago

   We 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.
7. 187.▲
   by shenli3514 9y ago

   Hi xmichael99, I'm a lead developer from TiDB, and thank you for voicing your experience regarding reporting bugs in our community. I can assure you that our team member would never ever offend you, or any other developer contributing
8. 188.▲
   TiDB Brings Distributed Scalability to SQL(thenewstack.io)

   4 points by shenli3514 9y ago|0 comments
9. 189.▲
   by shenli3514 10y ago

   Thanks for your attention.
10. 190.▲
    by shenli3514 10y ago

    Here is two examples about how to use TiKV's KV API: https://github.com/pingcap/tidb/blob/master/cmd/benchkv/main... https://github.com/pingcap/tidb/blob/mas
11. 191.▲
    by shenli3514 10y ago

    Please feel free to discuss in this google group or raise a new issue on github.
12. 192.▲
    by shenli3514 10y ago

    Yes, TiDB is a Relational database.
13. 193.▲
    by shenli3514 10y ago

    We use RocksDB as the single-machine storage engine and build TiKV above RocksDB as a distributed storage engine. At first we consider use Go to build TiKV, but the cgo overhead between TiKV and Rocksdb is considerable. So we turn to Rust.
14. 194.▲
    by shenli3514 10y ago

    There are two more things: 1. Go has high development efficiency. So we could build complex SQL logic easily. 2. Go is easy to write concurrent code. So we could enjoy the benefit of multi-core cpu. For example, we could use multiple gorout
15. 195.▲
    by shenli3514 10y ago

    Go code communicate with Rust code through network. So there is no overhead. Go has interface, which could be used for expressing the AST, plan tree. We define some interface for AST node and plan tree node. It is convenient to apply some r
16. 196.▲
    by shenli3514 10y ago

    Yes, Go has higher development efficiency than Rust, especially for new comers. For a storage engine, the most important thing is stable. We focus on write right and stable codes. Rust's compiler is quite strict. Which is good for writ
17. 197.▲
    by shenli3514 10y ago

    Go is good at concurrent concurrency and has great development efficiency. We could easily develop complex SQL logical and parallelize many operators. But its GC and cgo overhead is not suitable for developing storage engine. So we choose R
18. 198.▲
    by shenli3514 10y ago

    If there is a RDMS with great scale capacity, it will save the effort of data migration. Spark/Hadoop could read data from the RDMS directly.